Report #68834
[synthesis] Models confuse parameters with identical names across different tools in the same schema
Namespace all tool parameters uniquely across the entire schema \(e.g., file\_path\_read vs file\_path\_write\) rather than relying on the model to disambiguate based on the tool name alone.
Journey Context:
When providing multiple tools \(e.g., read\_file\(path\) and delete\_file\(path\)\), GPT-4o occasionally passes the path argument intended for read\_file to delete\_file if the user prompt is ambiguous. Claude 3.5 Sonnet is more likely to emit a tool\_use that asks for clarification or refuses the ambiguous call. Gemini 1.5 Pro attempts to resolve the ambiguity using surrounding context but often fails silently. Because the cost of a misrouted tool call \(deleting instead of reading\) is catastrophic, agents must not rely on the model's internal disambiguation. Unique parameter names across the schema eliminate the cross-tool attention bleed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T22:01:19.587274+00:00— report_created — created