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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: experimental status, live candidate testing with no candidate currently active, exact parity with ask_pipeworx at present, and the fallback behavior ('Falls back to nothing — this IS a full working router'). No contradiction with annotations.

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 key facts — beta, identical to ask_pipeworx, experimental edge, currently no active candidate — are front-loaded. However, the description is verbose (~100 words) with redundancy: 'identical universal router' is restated by the parenthetical 'same 5,798 tools, same arguments, same response shape,' and the final fallback sentence re-emphasizes the working-router point. Structured, but could be tightened.

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?

Given the tool's complexity (a universal router over 5,798 tools) and rich annotations, the description covers the essentials: current parity with the stable router, experimental risk, the evaluation purpose, and identical response shape to ask_pipeworx. It does not detail output structure, but that is inherited from the sibling and noted, so nothing critical is missing for selecting and calling this tool.

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 description coverage is 100%, so the schema documents every parameter; baseline is 3. The description's 'same arguments' reference ties parameters to ask_pipeworx and confirms the alias set, but adds no meaning beyond what the schema already provides. This is adequate but not additive.

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 states a specific verb+resource ('Beta version of ask_pipeworx... universal router') and immediately distinguishes it from the stable sibling by the experimental-edge angle. It is clear what the tool does, though the explanation leans on 'identical to ask_pipeworx' rather than standing entirely on its own.

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?

Explicitly instructs when to use it ('Use it exactly like ask_pipeworx when you want the newest routing') and notes results feed a merge decision against the stable router. It lacks explicit when-not-to-use phrasing or mention of ask_pipeworx_grounded, but the context is concrete enough to route an agent correctly.

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