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

Annotations already declare readOnly/idempotent/openWorld, and the description adds genuine behavioral context beyond them: no fallback behavior, live candidate routing, and background comparison against the stable router. It does not cover latency or rate-limit characteristics, but the experimental semantics are unusually well disclosed.

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?

Front-loads the key identity ('Beta version of ask_pipeworx') and stays to one paragraph, but repeats the equivalence point three times (same arguments/response shape, currently matches exactly, falls back to nothing). Slightly redundant, though each clause is informative.

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?

With no output schema, the description carries the return-shape burden and discharges it by stating the response shape matches ask_pipeworx. For a router tool with annotation-covered safety, the only remaining gap is present-tense guidance on whether to use it at all while no candidate is active.

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% and the schema already documents all six aliases mapping to 'question.' The description only adds that arguments are identical to ask_pipeworx, which does not extend parameter meaning beyond the schema, so baseline 3 is appropriate.

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 beta) and explicitly contrasts itself with the sibling ask_pipeworx, noting identical tool count, arguments, and response shape. An agent can distinguish it from ask_pipeworx without opening either 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 clear condition: 'Use it exactly like ask_pipeworx when you want the newest routing,' and explains that results are compared against the stable router. It does not explicitly say when to prefer the stable ask_pipeworx instead, and the statement that it currently matches ask_pipeworx exactly leaves the agent to infer whether there is any present reason to choose it.

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