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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new context: the experimental routing state, that no candidate is currently active, the evaluation/merge pipeline, and that there is no fallback degrade path. Missing auth/rate-limit or latency notes, and the return shape is only asserted as 'same as ask_pipeworx' rather than described.

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 routing status and sibling equivalence are front-loaded in the first sentence, and the final sentence preempts the reasonable 'is beta degraded?' concern. There is mild redundancy between 'identical … same arguments, same response shape' and 'Use it exactly like ask_pipeworx,' which costs a point.

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 read-only router with 100% parameter coverage and no output schema, the description covers the essentials: scope, sibling equivalence, current experimental state, invocation pattern, and fallback behavior. Nothing an agent needs in order to choose and call it correctly is missing.

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 alias fields and pack scoping are already fully documented in the schema, including the ignored-slug and full-catalog fallback behavior. The description contributes only 'same arguments' and adds no semantics beyond that, 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 a specific verb+resource ('universal router' over 7,132 tools) and explicitly positions itself against its sibling ask_pipeworx, noting identical arguments and response shape. An agent can tell immediately this is the experimental twin of the stable router rather than a distinct capability.

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 clear selection rule: 'Use it exactly like ask_pipeworx when you want the newest routing,' and explains the tradeoff (results compared against the stable router). It stops short of an explicit when-not-to-use clause (e.g., 'prefer ask_pipeworx for production answers' or routing grounded questions to ask_pipeworx_grounded), leaving that inference to the agent.

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