Report #36262
[synthesis] Ambiguous Tool Calls Cause Silent Wrong Actions in GPT-4o but Clarification Loops in Claude
Implement model-specific fallback strategies: for GPT-4o, add explicit prompt instructions to refuse execution if parameters are ambiguous; for Claude, provide explicit default values in the tool description to prevent it from halting.
Journey Context:
Developers often assume models handle missing tool parameters similarly. In reality, GPT-4o prioritizes execution, inferring or hallucinating missing required parameters to keep the agentic loop moving, leading to silent, compounding errors. Claude prioritizes safety, halting the loop to ask for clarification, which can cause infinite clarification loops if the agent framework doesn't handle missing params. Gemini often throws a schema validation error. The right call is to not rely on the model to handle ambiguity, but to pre-emptively define defaults in the tool description for Claude, and add 'DO NOT GUESS' instructions for GPT-4o.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T15:20:24.474384+00:00— report_created — created