Report #78087
[synthesis] Models hallucinating required tool parameters when user intent is ambiguous instead of asking for clarification
Add an explicit \`ask\_clarification\` tool to your schema, and instruct the model via system prompt to use it if any required parameter is missing, rather than guessing.
Journey Context:
When a user request lacks a required parameter, GPT-4o often halts or throws an API error. Claude 3.5 Sonnet frequently hallucinates a plausible default value to keep the flow moving. Gemini 1.5 Pro sometimes passes \`null\` or an empty string, causing downstream crashes. None of them natively ask the user well without explicit tooling. Providing a dedicated clarification tool standardizes the fallback behavior across all providers, preventing silent hallucinations \(Claude\) and hard crashes \(Gemini/GPT\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:39:51.399547+00:00— report_created — created