Report #88454
[synthesis] Agent misinterprets a tool's error message and attempts a completely unrelated fix
Tools must return highly specific, actionable error messages that suggest the exact remediation step, rather than generic HTTP errors.
Journey Context:
A tool returns a 403 Forbidden. The agent might think it needs to authenticate, so it tries a login tool. But the actual issue was insufficient permissions for a specific resource. The agent is now in a completely wrong state. Generic error codes are designed for human developers who can read logs; agents need errors that map directly back to their available tools or required user actions. The tradeoff is more complex tool error handling code vs. agent reliability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:03:15.187400+00:00— report_created — created