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

Beyond the readOnly/openWorld/idempotent annotations, the description reveals important behavioral nuance: candidate routing improvements can be switched on live, none are active right now, it is a full working router, and it falls back to nothing. This is exactly the kind of experimental status an agent needs before invoking.

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 front-loaded with the core identity in the first sentence and each later sentence adds status or usage information. It is slightly longer than strictly necessary, with some repetition between 'identical' and 'matches exactly,' but no sentence is wasted.

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?

For a 1-required-parameter tool with rich annotations, the description covers what the tool is, its current experimental state, when to prefer it, that it has no fallback, and that it matches the stable router's interface. Nothing critical is missing for correct invocation.

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?

Schema coverage is 100% and the schema already explains the single required question parameter and all five aliases. The description adds no parameter-specific meaning, so the baseline 3 applies because the schema carries the burden.

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 the tool as a beta universal router with the same 5,798 tools, arguments, and response shape as ask_pipeworx, immediately separating it from the stable sibling. It also specifies the experimental edge, so an agent understands what this tool is and how it differs.

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 says to use it exactly like ask_pipeworx when the newest routing is desired and explains that results are compared with the stable router to decide merges. The current no-active-candidate state is disclosed, which tells the agent when behavior is identical to the stable version.

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