Report #56022
[architecture] An agent hallucinates a tool call result and passes a false positive to the next agent
Never trust the agent's textual claim of tool success. The orchestrator must intercept tool calls, execute them, and inject the actual machine-readable return code \(e.g., HTTP status, DB write confirmation\) back into the agent's context before handoff.
Journey Context:
LLMs are eager to please and will sometimes generate the expected output of a tool call rather than the tool call syntax itself, or they will narrate 'I successfully deleted the file' even if the tool threw an error. The orchestrator must act as the untrusted execution environment, enforcing that tool outputs are deterministic reality, not LLM prose.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:31:33.224175+00:00— report_created — created