An Agent connected to hundreds of tools may still fail to improve its task completion rate. The problem may not be the model, but how many tools it “sees” in each turn. The original article reminds us that more tools do not necessarily mean better usability: what determines success is the selection and presentation strategy.

What this is

An Agent is an AI assistant that can call tools step by step to accomplish a goal. It typically works with a set of tool descriptions covering functionality, required fields, and usage formats. Showing all descriptions at once consumes the model’s limited information-processing capacity; tokens can be roughly understood as the unit of textual information a model can process.

Two things need to be distinguished here. The capability model determines whether a tool is built as a specialized function, a general-purpose command, or a Skill—a set of instructions explaining how to perform a particular type of task, optionally with attached scripts. The presentation strategy determines how many tools the Agent sees at the current moment. A more common design is to provide a short directory first, expand the relevant descriptions as the task progresses, and even let the Agent search for tools on demand when needed.

MCP (Model Context Protocol, a standard interface for connecting AI applications to external services) solves the problem of how tools connect. It does not decide which tools should be exposed in a given turn. Skill Hub is closer to a distribution channel for operating instructions.

Industry view

We believe the industry is shifting from “connection count” to “tool governance.” For builders, the key metric is not how many services they have connected, but whether they can find the right tool, clearly say “not found” when no suitable option exists, and restrict the data and system permissions available to tools.

On-demand discovery, however, has not been fully validated. The test cited in the original article used Qwen3-4B and covered only three tasks. Both the all-at-once and on-demand discovery groups completed all three tasks, achieving an accuracy rate of 100%. The test shows only that active discovery reduced the volume of exposed descriptions and the measured execution time, while also producing irrelevant calls and premature termination. It cannot support the claim that on-demand approaches generally improve accuracy.

The risks are equally concrete: third-party tool descriptions may contain prompt-injection instructions, and scripts attached to Skills may execute local code. Searchability and installability do not mean that access to contacts, email, or other permissions should be granted immediately. Sources, versions, and access scopes should all be reviewed.

Impact on regular people

For enterprise IT: When evaluating AI assistants, procurement teams should shift their focus from tool count to selection mechanisms, invocation logs, and permission boundaries, avoiding products that offer “many features but a chaotic selection process.”

For individual professionals: An Agent purchased by an employer is not necessarily better because it connects to more tools. A more reliable assistant understands what the current task requires and can stop and explain why when no suitable tool is available.

For the consumer market: Connections between applications will become more widespread, but the difference users actually experience will not be “how many services are supported.” It will be whether an assistant requires fewer steps, completes tasks accurately, and gives users control over sensitive-data permissions.