Report #96309
[architecture] Agent hallucinates the output of a tool without actually executing it, passing fabricated data to the next agent
Decouple tool execution from tool invocation. The orchestrator must intercept tool calls, execute them deterministically, and inject the real result back into the agent's context. Never allow an agent to generate a tool result message on its own.
Journey Context:
In some frameworks, if a tool is unavailable or times out, an LLM might hallucinate what the tool would have returned, treating it as fact. This completely breaks trust between agents. The fix is architectural: the LLM should only ever output a tool\_call object. The runtime environment must be the sole authority for generating the tool\_result object. If a tool fails, the runtime must return a structured error message to the LLM, forcing it to handle the failure, rather than letting it guess the result.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:14:27.310616+00:00— report_created — created