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

The description adds important context beyond the readOnly/openWorld/idempotent/destructive annotations: it is a beta with live candidate routing, currently matches ask_pipeworx exactly because no candidate is active, and it has no fallback — it is a full working router on the experimental edge. This meaningfully informs agent expectations.

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 somewhat long but every sentence contributes: identity, current status, usage guidance, and no-fallback behavior. The key differentiators are front-loaded, and the tone is direct without wasted words.

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 single-required-parameter tool with no output schema, the description covers what the tool is, its current behavior, when to use it, and what distinguishes it from ask_pipeworx. It relies on the sibling description for full response semantics, but 'same response shape' is sufficient in this context.

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?

The input schema already documents all six parameters at 100% coverage, including the question parameter and its aliases. The description only says 'same arguments' as ask_pipeworx, which adds no new parameter-level meaning 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 states clearly that this is a beta universal router identical to ask_pipeworx, with the same 5,798 tools, arguments, and response shape. It differentiates from the stable ask_pipeworx by positioning itself as the experimental edge with candidate routing improvements.

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 to use this when you want the newest routing and notes that results are compared against the stable router. It does not explicitly list when-not-to-use conditions, but the beta/experimental framing and stable alternative are clearly implied.

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