Report #76638
[synthesis] Identical ambiguous tool calls yield different structural outputs across models
Explicitly define defaults in the tool schema description and enforce required fields strictly; do not rely on the model to infer missing parameters consistently.
Journey Context:
Developers often assume LLMs handle missing tool parameters like standard API clients \(using defaults\). But LLMs treat missing parameters as ambiguous prompts. Claude's refusal breaks agentic loops waiting for a tool call; GPT-4o's hallucination breaks downstream validation; Gemini sends nulls. Explicitly stating 'If not provided, do X' in the description aligns behavior.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:13:56.376087+00:00— report_created — created