Report #21533
[architecture] Agent passes raw, unverified tool error output to downstream agent, causing hallucination
Intercept tool execution results at the orchestrator level. If a tool returns an error code/exception, do not pass the raw stack trace to the next agent. Map it to a semantic error message or trigger a recovery agent.
Journey Context:
When Agent A uses a tool that fails \(e.g., HTTP 500\), the raw error string is often dumped into A's context. A then passes this to B, who might hallucinate a solution based on the stack trace. The orchestrator must act as a circuit breaker and translate system errors into LLM-friendly semantic failures, preventing the model from overfitting to irrelevant system noise.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:33:41.353016+00:00— report_created — created