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

The description openly discloses that this is an experimental beta variant, that candidate routing improvements may be enabled live, that none are currently active, and that results are compared against the stable router. The read-only/idempotent annotations are not contradicted by the text.

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 beta identity and then gives current status and usage direction; no sentence is wasted. Some redundancy exists between 'currently matches ask_pipeworx exactly' and the later 'full working router' clarification, but it is intentional emphasis rather than bloat.

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?

The description covers current behavior, relationship to the stable router, and input expectations, which is sufficient for calling the tool without an output schema. It relies on prior knowledge of ask_pipeworx for specifics such as the response format, though it does state that the response shape is identical.

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?

All six parameters are string aliases for the question, and the question description explicitly lists the accepted aliases, giving full coverage of the schema. The description does not provide examples or formatting guidance, but none are needed for a free-form natural-language parameter.

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 identifies it as a beta version of ask_pipeworx and an identical universal router with the same tools, arguments, and response shape, making its general purpose clear. It stops short of explaining what 'universal router' does in plain terms, so an agent unfamiliar with ask_pipeworx would need to infer the behavior.

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 clarifies that no candidate is active so it currently matches the stable router. It does not contrast directly with sibling options like ask_pipeworx_grounded, but the primary selection condition is stated.

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