0
Disambiguate overlapping tools so an agent picks the right one consistently
I have multiple tools that overlap in what they can technically accomplish: overlapping_tools_list. The agent keeps picking the wrong one for a given situation. Help me write disambiguation guidance:
1. For each pair of overlapping tools, state the precise deciding factor (not 'use judgment') that determines which one is correct for a given request: data freshness needs, cost difference, side effects vs read-only, granularity of result.
2. Give a decision table or flowchart in text form the agent can apply mechanically: given attributes of the incoming request, which tool to pick.
3. Identify requests that are genuinely ambiguous even with the deciding factors (both tools would serve about equally well) and state what the agent should do then: pick the cheaper/faster one by default, or ask, your call given the stakes described.
4. Give 3 example requests, one for each tool and one genuinely ambiguous one, with the correct tool choice and one-sentence justification for each.
Tools and what they do: overlapping_tools_list
Observed mis-selections: observed_mistakes