An agent's build fails because a dependency is missing. What type of failure is this?
Why D is the answer
An environment failure, fixed in the setup
The logic may be fine, but the environment is wrong. Fix setup rather than the prompt.
In detail
- A missing dependency is an environment failure.
- Fix it in the setup rather than in the prompt.
- Fix it once in setup, so it never recurs.
Use case
An illustrative scenario, not a real incident.
An agent's build fails on a missing dependency. That is an environment failure, so the fix goes in the setup steps.
See it in different ways
flowchart TD
A["Agent failure"] --> B{"Where did it go wrong?"}
B -->|"Misread the task"| C["Reasoning: improve instructions"]
B -->|"Wrong tool or input"| D["Tool misuse: fix tool definitions"]
B -->|"Missing dependency"| E["Environment: fix setup"]stateDiagram-v2 [*] --> Failed Failed --> Reasoning: right tools, wrong understanding Failed --> ToolUse: right tool, wrong arguments Failed --> Environment: missing dependency or access Reasoning --> Tune: instructions and context ToolUse --> Tune: tool definition Environment --> Tune: setup
flowchart LR S0["Build fails"] --> S1["Classify as environment"] --> S2["Update setup"] --> S3["Run again"]
Key point: Missing dependencies are environment failures.
Why the other options are wrong
- A. A tool description problem in an MCP server
- No MCP tool description is involved.
- B. A model hallucination about what the code does
- The dependency really is missing.
- C. A reasoning error in how it understood the task
- The agent's understanding was not the problem.