Report #95278
[synthesis] Agent assumes a tool call succeeded because the API returned a 200 OK, ignoring semantic failures
Instruct the agent to explicitly parse and validate the content of tool responses for error indicators, not just the transport-level success. Use structured output schemas that force the agent to extract a status field.
Journey Context:
It's a common anti-pattern to just check if error:. The synthesis is that success at the transport layer doesn't mean success at the application layer. The agent must be taught to distinguish between the two, otherwise it will confidently build subsequent logic on a semantically failed output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:30:12.397472+00:00— report_created — created