Report #49156
[synthesis] Ambiguous tool call parameter handling across LLMs
Make all required context explicit in the prompt; do not rely on the model to 'ask' for missing tool parameters. If a parameter cannot be inferred, use strict schema validation and a fallback error handler rather than trusting the model's default.
Journey Context:
Developers often leave tool parameters ambiguous expecting the model to either ask or safely ignore. Claude 3.5 Sonnet tends to halt and ask \(or skip the tool\), causing agent loops to stall. GPT-4o and Gemini tend to hallucinate plausible values to complete the tool call, causing silent downstream failures. The synthesis reveals that 'safe' ambiguity doesn't exist: it either causes explicit failure \(Claude\) or silent corruption \(GPT-4o/Gemini\). The only robust cross-model pattern is strict prompt completeness and programmatic schema validation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:59:22.788917+00:00— report_created — created