Handling Hundreds of Agent Tools

An enterprise may own hundreds or thousands of capabilities, but one model turn should usually see a much smaller relevant set.

Partition by domain

Separate finance, CRM, code, operations, and analytics into coherent capability boundaries rather than one universal server.

Filter dynamically

Use user role, task, workflow stage, and prior routing decisions to reduce the candidate tool set.

Deferred discovery

Some runtimes can discover or load tools only when the model indicates a relevant domain. This can preserve context and reduce decision noise.

Evaluate descriptions

Run a routing benchmark: given representative prompts, does the model choose the right tool? Rename and rewrite descriptions based on measured confusion.