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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, but the description adds meaningful context: it is a live experimental edge, candidates can be enabled at any time, it currently matches ask_pipeworx exactly, and it 'falls back to nothing' as a full working router rather than a stub. This goes beyond the structured hints and gives a clear behavioral model.

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 dense and front-loaded with the tool's identity and relationship to ask_pipeworx. Each sentence adds useful operational information, though phrases like 'identical universal router' alongside 'same 5,718 tools, same arguments, same response shape' are slightly redundant. Overall it is appropriately sized for a beta tool with an important distinction.

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 router tool with no output schema, the description covers the essential context: what it routes to, why it is experimental, current status, how to use it, and that it is not a fallback. The 'same response shape' reference provides return-value context by analogy to ask_pipeworx. It could be improved by explicitly describing the output shape, but the current coverage is strong.

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%, with each parameter described as an alias for 'question' and a clear natural-language description on the question field itself. The description says 'same arguments' but adds no semantic detail beyond what the schema already provides. Baseline 3 is appropriate because the schema handles parameter meaning fully.

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 clearly identifies the tool as a beta version of ask_pipeworx, a universal router that dispatches to 5,718 tools. It explicitly states it uses the same arguments and response shape, and differentiates itself from the stable sibling by its experimental routing edge. An agent can understand what this tool does and how it differs from ask_pipeworx without opening the 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?

The description explicitly says to use it like ask_pipeworx 'when you want the newest routing' and notes that results are compared against the stable router. It also clarifies that no candidate is active right now, so behavior currently matches the stable tool. However, it lacks an explicit when-not-to-use statement, though the contrast with the stable router implies the stable alternative.

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