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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower; the description nonetheless adds live-state and evaluation context the annotations cannot convey — that candidate routing is enabled only while one is under test, that none is active as of 2026-07-26, and that calls are compared against the stable router. The explicit 'Falls back to nothing — this IS a full working router' preempts the natural worry that a beta tool might be a stub. It does not say whether beta calls are logged or shared, which is the one behavioral trait an agent might want.

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 critical framing (beta router, currently identical to stable) is front-loaded, and every sentence is on-topic. There is mild redundancy between 'same 7,133 tools, same arguments, same response shape' and 'currently matches ask_pipeworx exactly', and the retired-candidate date is arguably detail an agent cannot act on.

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 9-parameter (1 required) router with no output schema, the description covers the operational essentials: what it routes to, how it differs from stable, and that it never falls back to nothing. Return values are only gestured at via 'same response shape' as ask_pipeworx, which is adequate only because that sibling's definition is visible, but it would be stronger if the response envelope or the _meta fields were acknowledged here.

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% and the six alias parameters plus `packs` are fully documented in the schema, including the ignored-slug and full-catalog fallback behavior. The description adds nothing parameter-specific beyond 'same arguments' as ask_pipeworx, so the baseline 3 applies.

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?

States exactly what the tool is: the beta instance of the ask_pipeworx universal router, with the same 7,133 tools, arguments and response shape. It anchors itself against the named sibling ask_pipeworx and against ask_pipeworx_grounded implicitly, so an agent can tell the three apart without opening a schema.

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?

Gives a concrete selection rule — 'Use it exactly like ask_pipeworx when you want the newest routing' — and names the stable alternative it is compared against. It stops short of an explicit 'do not use this for production/reliable answers', and it undercuts itself by noting it currently matches ask_pipeworx exactly, leaving the agent to decide whether that means 'equivalent, pick either'.

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