Report #96991
[research] Generating the expected tool output instead of actually calling the tool, or fabricating the tool's return value
Enforce strict separation between tool call generation and tool execution. The model must output a structured tool call command and halt; it must never simulate the tool's JSON response.
Journey Context:
In agentic workflows, models sometimes 'jump the gun' by predicting what a tool \(like a web search or code interpreter\) will return, and then answering based on that hallucinated return. This completely defeats the purpose of grounding. Enforcing a stop token after the tool call syntax is mandatory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:22:55.667773+00:00— report_created — created