Report #6917
[agent\_craft] Agent hallucinates tool results or fails to reason about multi-step dependencies
Structure the system prompt to enforce ReAct pattern: alternate explicit Thought/Action/Observation cycles. Force the model to output reasoning \(Thought\) before every tool call \(Action\), then wait for the observation result before continuing. Use XML tags like and to enforce the structure.
Journey Context:
Direct tool chaining fails because the model lacks scratchpad reasoning. ReAct \(Reasoning \+ Acting\) creates a loop where the model must articulate why it's calling a tool and what it learned from the result. This prevents hallucinated tool outputs and enables recovery from tool errors by explicitly reasoning about the failure in the next Thought step. Simple zero-shot tool instructions often lead to the model assuming tool outputs without calling them.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T01:19:55.394702+00:00— report_created — created