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

Annotations already establish read-only, idempotent behavior, and the description adds meaningful operational context: no candidate is currently active, it matches ask_pipeworx exactly, and it 'falls back to nothing' — clarifying it is a fully working router, not a stub. It also explains that its output is compared against the stable router.

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 information-dense and front-loaded with the beta identity. There is mild redundancy ('identical universal router' repeated with 'same 5,724 tools' and 'use it exactly like ask_pipeworx'), but each sentence earns its place.

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 router with no output schema, the description adequately references 'same response shape' and directs usage to ask_pipeworx, covering gaps. It does not describe the response format itself, but the sibling context and schema make this sufficient.

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% with all six parameters documented as aliases of 'question.' The description adds no parameter-level detail, but it doesn't need to because the schema is self-sufficient.

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 version of ask_pipeworx' — a universal router that forwards questions to a large toolset. It differentiates from the stable sibling by calling out candidate routing improvements and the beta status, making its role unmistakable.

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 instructs 'Use it exactly like ask_pipeworx when you want the newest routing,' giving a concrete condition for preferring this tool. It stops short of naming exclusions (e.g., 'use ask_pipeworx when you need stable results'), but the beta framing implies this trade-off.

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