Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly and idempotent annotations, the description discloses that candidate routing improvements can be enabled live, that none is currently active, that it currently matches ask_pipeworx exactly, and that it does not fall back to another tool. This gives the agent important behavioral context about potential variability.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat verbose with historical details, but the key facts are front-loaded and each sentence adds transparency about beta status, current equivalence, and usage intent. The redundancy around matching ask_pipeworx is minor given the importance of setting expectations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description could explain the exact response shape more concretely, but it does say the response shape is identical to ask_pipeworx, which is a useful anchor. The input side is fully covered by the schema, and the tool's experimental nature and fallback behavior are well documented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% coverage for the parameters, including aliases q, text, and input. The description only says 'same arguments' as ask_pipeworx, which confirms consistency but does not add meaningful semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies this as a beta universal router with the same 5,798 tools, same arguments, and same response shape as ask_pipeworx, while explicitly distinguishing it as the experimental edge. This sets clear expectations that it is not the stable router.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states to use it exactly like ask_pipeworx when the newest routing is desired, and clarifies that results are compared against the stable router to decide merges. The alternative ask_pipeworx is implicitly the stable choice when experimental routing is not wanted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.