Report #51083
[architecture] Agent hallucinates tool execution success, passing false confirmation to the next agent
Never trust an agent's textual claim of tool success. The orchestrator must verify tool execution by checking the actual tool return payload \(e.g., HTTP status, database confirmation ID\) and inject the verified result into the next agent's context.
Journey Context:
LLMs will sometimes output 'I have successfully updated the file' without actually invoking the tool, or the tool returns an error and the LLM ignores it. The handoff contract must be based on the actual tool output, not the LLM's summary of it. The orchestrator acts as the execution environment, binding tool outputs directly to the state. Tradeoff: Requires the orchestrator to intercept and parse tool outputs rather than letting agents manage their own execution loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:13:51.905152+00:00— report_created — created