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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is established. The description adds valuable non-obvious behavior: it is a fully working router with no fallback, is currently identical to the stable ask_pipeworx, and may change when a candidate is under test. No contradiction with annotations exists.

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 primary purpose and beta status in the first sentence. It conveys current behavior, experimental nature, and usage guidance in four sentences. Minor redundancy around 'full working router' and 'falls back to nothing' exists, but it does not meaningfully detract.

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 100% schema coverage, rich annotations, and a single required input, the description provides enough context for invocation. It does not detail the response shape beyond 'same response shape,' but because this is explicitly a beta alias of a known sibling router, that reference is reasonably complete. The absence of an output schema is partially compensated by the explicit parity statement with ask_pipeworx.

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%, with every parameter (question plus five aliases) already documented in the input schema. The description only says 'same arguments' without adding new semantic meaning or clarifying parameter usage beyond the schema. This aligns with the baseline of 3 when the schema already handles parameter documentation.

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 opens with 'Beta version of ask_pipeworx: identical universal router' and clearly identifies this as the experimental variant of the stable router. It distinguishes itself from ask_pipeworx and the grounded sibling by tying it to 'candidate routing improvements' and the 'experimental edge,' so an agent can tell which tool is being described.

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 'Use it exactly like ask_pipeworx when you want the newest routing' and notes that results are compared against the stable router, which gives clear when-to-use guidance. It also says no candidate is active right now, so it currently matches ask_pipeworx exactly. It does not explicitly mention when not to use it or name the grounded alternative, but the routing-intent guidance is sufficient.

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