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

The annotations already mark it read-only and non-destructive, but the description adds critical context beyond that: experimental routing improvements can be live, none is active now, and results are compared against the stable router. This gives an unusually clear picture of reliability and current behavior.

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?

Four sentences each serve a distinct purpose: identity, current status, usage guidance, and reliability caveat. It is front-loaded with the core purpose and contains no redundant or filler sentences.

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?

The description covers everything an agent needs beyond the schema and annotations: experimental nature, current parity with the stable router, comparison behavior, and fallback semantics. It also references the same response shape as ask_pipeworx, which adequately compensates for the absent output schema.

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 already documents the question field and its five aliases. The description adds only that the arguments match ask_pipeworx, which is useful context but does not meaningfully deepen parameter understanding beyond the schema.

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 explicitly identifies this as a beta version of ask_pipeworx and calls it a universal router, specifying exactly what is identical: 5,724 tools, same arguments, and same response shape. This clearly differentiates it from the stable ask_pipeworx sibling and the grounded variant.

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 gives an explicit use condition: use it exactly like ask_pipeworx when you want the newest routing. It also clarifies the current no-candidate state and states that this is a full working router, not a fallback, so an agent knows when and how to invoke it.

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