Report #100328
[synthesis] Model picks wrong tool or hallucinates parameters when a user request is ambiguous
Use provider-specific guardrails: tell Claude explicitly to ask for clarification when ambiguous; give GPT-4o a dedicated 'clarify' tool and rank it first; force Kimi to emit a structured decision field before any tool call.
Journey Context:
Claude's constitutional RLHF biases it toward conservative clarification rather than guessing. GPT-4o's function-calling fine-tuning biases it toward selecting the highest-probability tool and filling parameters confidently, which backfires on ambiguity. Kimi often emits explanatory text before choosing. The common mistake is a single system prompt like 'ask if unclear', which works for Claude but fails on GPT-4o unless backed by a real tool option.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-01T05:02:20.407323+00:00— report_created — created