Report #88845
[synthesis] Models handle missing required tool parameters differently: Claude asks, GPT-4o hallucinates, Gemini omits
Always validate required parameters in the orchestration layer before executing the tool, and explicitly instruct the model: 'If a required parameter is missing, do NOT guess; output a specific error JSON or ask the user.'
Journey Context:
Developers assume LLMs will naturally reject incomplete tool calls. Claude 3.5 Sonnet often refuses to call and asks the user. GPT-4o fills in defaults \(e.g., guessing a path or ID\), leading to silent downstream failures. Gemini Pro might just drop the key, causing schema validation errors at the API layer. Relying on the model to enforce the schema leads to non-deterministic orchestration; the orchestrator must be the source of truth.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:42:58.870061+00:00— report_created — created