AI Agent Failure Modes: The Eight Ways Autonomous Agents Break

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

1. “The honest answer is almost always one of eight things, and the eight things are different enough that lumping them together as "the agent broke" loses the information needed to fix the problem.” The eight categories are the same eight that drive the 80-test methodology in how we test AI agents. Generalised here for buyers and operators who want to recognise failures in their own agents, not just understand the testing.

   In AI SDR agent failure modes

2. 1. Input variation “The same intent phrased differently produces different behaviour.” Defence: explicitly test paraphrases. The input-variation category in the 80-test methodology runs ten paraphrases of the same intent for every capability. Defences include broader tool descriptions, fewer hard-coded phrasings in the system prompt, and giving the agent room to reason about what the user means rather than match keywords.

   In AI SDR agent failure modes

3. 1. Input variation “Input variation failures appear when the agent's prompt or tool descriptions over-fit to specific phrasings.” Defence: explicitly test paraphrases. The input-variation category in the 80-test methodology runs ten paraphrases of the same intent for every capability. Defences include broader tool descriptions, fewer hard-coded phrasings in the system prompt, and giving the agent room to reason about what the user means rather than match keywords.

   In AI SDR agent failure modes

4. 1. Input variation “"Send a follow-up to leads who haven't replied in 5 days" works; "ping unresponsive leads from last week" surfaces a different lead set or fails to find any.” Defence: explicitly test paraphrases. The input-variation category in the 80-test methodology runs ten paraphrases of the same intent for every capability. Defences include broader tool descriptions, fewer hard-coded phrasings in the system prompt, and giving the agent room to reason about what the user means rather than match keywords.

   In AI SDR agent failure modes

5. The same intent phrased differently produces different behaviour. "Send a follow-up to leads who haven't replied in 5 days" works; "ping unresponsive leads from last week" surfaces a different lead set or fails to find any. Input variation failures appear when the agent's prompt or tool descriptions over-fit to specific phrasings. “The input-variation category in the 80-test methodology runs ten paraphrases of the same intent for every capability.” 2. Tool failure

   In AI SDR agent failure modes

6. The same intent phrased differently produces different behaviour. "Send a follow-up to leads who haven't replied in 5 days" works; "ping unresponsive leads from last week" surfaces a different lead set or fails to find any. Input variation failures appear when the agent's prompt or tool descriptions over-fit to specific phrasings. “Defences include broader tool descriptions, fewer hard-coded phrasings in the system prompt, and giving the agent room to reason about what the user means rather than match keywords.” 2. Tool failure

   In AI SDR agent failure modes

7. How do you debug AI agent failures? “Input variation: add paraphrase tests. Tool failure: add retry with exponential backoff. Partial results: tighten stopping conditions. Hostile input: strengthen prompt-level refusal policy.” Are AI agent failure modes deterministic?

   In AI SDR agent guardrails

8. A downstream API returns 5xx, times out, or returns a malformed payload. The agent now has a partial state: did the action happen or not? Tool failures are the most common reason agents stop mid-task in production. “The default should be safe-stop; the exception is when the tool's idempotency guarantees allow safe retry.” 3. Partial results (the "stop after one task" failure)

   In Outbound stack resilience

Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.