Report #71382
[synthesis] Agent selects wrong tool when multiple tools have overlapping functionality
When defining overlapping tools, place the preferred tool first in the array for GPT-4o. For Claude, make tool names and descriptions highly distinct using domain-specific jargon. For Gemini, ensure parameter schemas differ significantly between overlapping tools.
Journey Context:
When presented with two tools having overlapping functionality \(e.g., \`search\_web\` and \`search\_database\`\), GPT-4o exhibits a positional bias, defaulting to the tool defined first in the API payload. Claude 3.5 Sonnet attempts to resolve ambiguity by filling parameters for both tools or halting with a natural language clarification, while Gemini 1.5 Pro matches based on parameter name similarity, ignoring the tool name itself. A single strategy doesn't work; you must tailor tool definitions to the specific model's selection heuristic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:23:36.533617+00:00— report_created — created