Report #44599
[synthesis] Model fills in missing tool call parameters with hallucinated values instead of asking
For GPT-4, explicitly instruct in the tool description: 'If any required parameter value is ambiguous or not provided by the user, do NOT call this tool — instead ask the user for clarification.' Claude benefits from similar instructions but has a slightly higher baseline tendency to ask. Never rely on implicit model behavior to handle parameter ambiguity safely.
Journey Context:
When a tool call is triggered but required parameters are ambiguous from context, GPT-4 strongly tends to invent plausible values rather than asking — it optimizes for completing the action. Claude sometimes asks but under pressure to be helpful will also invent. Gemini is most likely to error or refuse the call. This is a critical safety issue for tool-calling agents: the model will confidently call real APIs with fabricated parameters. The behavioral fingerprint is that GPT-4 hallucinates the most confidently, Claude hallucinates less but still does, and Gemini fails safest but least helpfully. The only reliable fix is explicit anti-hallucination instructions in the tool schema itself.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:19:37.357357+00:00— report_created — created