Tools / Methods
verifiedTool Selection
Given fifty tools and a request, which one — and is the answer none of them? Selection is a retrieval problem before it is a reasoning one, and it degrades in a specific way: past a few dozen tools the model stops reading them all carefully and starts pattern-matching on names.
The scaling fix is the same as everywhere else in this graph — retrieve a shortlist, then decide among it — which turns tool selection into a Dense Retrieval problem over descriptions. The harder failure is the negative case: a model that always picks something will pick wrongly rather than say no tool applies, and that behaviour has to be trained or prompted for rather than assumed.
With n tools in context the selection is an n-way choice whose difficulty grows with description similarity rather than with n itself: two tools that differ in one clause are harder to separate than twenty that do different things. Retrieval reduces n to k before the choice, so accuracy depends on recall@k — a tool that is not shortlisted cannot be selected however well the model reasons.
tools-in-context holds 50% of the budget; rest holds the remaining 50%.
Tools placed in context against the room left for the task itself, in equal units. Drag the catalogue up to watch the tools crowd out the request — which is the reason to retrieve a shortlist rather than paste the list.
Reviewed by opendroid · 2026-08-18
- arXiv:2305.15334 — Gorilla: Large Language Model Connected with Massive APIs
- arXiv:2308.03688 — AgentBench: Evaluating LLMs as Agents