Report #85360
[synthesis] Ambiguous tool calls yield hallucinated defaults instead of clarification
Add explicit instruction in the system prompt: 'If a required parameter is ambiguous or missing from the user request, do NOT guess; instead, ask the user for clarification.' For GPT-4o, enforce this via a dedicated clarify tool; Claude often does this natively but needs the prompt to avoid edge-case guessing.
Journey Context:
When faced with an ambiguous request \(e.g., 'book a flight to London' without a date\), GPT-4o frequently hallucinates a default \(e.g., tomorrow's date\) to fulfill the tool call. Claude 3.5 tends to ask the user for the missing parameter. Relying on model-native clarification fails for OpenAI models, leading to silent, dangerous actions. Providing a ask\_clarification tool forces GPT-4o into a structured clarification path.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T01:51:54.915187+00:00— report_created — created