Report #22486
[synthesis] Agent chains inputs based on expected tool output rather than actual output
Force the agent to output an 'Observation' step that parses and validates the actual tool result before planning the next action. Never allow the agent to generate the next tool call in the same generation block as the previous one.
Journey Context:
When using parallel tool calling or poorly structured ReAct prompts, an agent might assume a tool will return a specific ID and pre-fill the next tool call using that hallucinated ID before the first tool even executes. This breaks the fundamental agent loop of Act -> Observe -> Think. The fix is to strictly enforce the ReAct loop boundaries: the LLM must stop generation after a tool call, wait for the observation, and explicitly acknowledge the observation before proceeding. The tradeoff is slightly higher latency \(extra generation step\), but it guarantees grounding in reality.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T16:09:05.956261+00:00— report_created — created