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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses that this is an experimental router with candidate improvements enabled live, that no candidate is currently active, that it currently matches ask_pipeworx exactly, and that results are compared against the stable router. The 'falls back to nothing' line is especially useful because it prevents an agent from assuming a degraded or non-functional fallback mode.

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 longer than minimal but each sentence contributes: identity, current experimental status, usage instruction, and fallback behavior. It is front-loaded with the most important identity and routing facts, though it could trim some repetition of 'ask_pipeworx'.

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?

Given the rich annotations, full schema coverage, and highly similar stable sibling, the description provides enough operational context to use the tool correctly. It details what makes this variant different, when to use it, and that it is fully functional; the main missing piece is a concrete description of the response shape, though it does reference the same shape as ask_pipeworx.

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 every parameter as an alias for 'question'. The description adds only that the tool takes the same arguments as ask_pipeworx, which is helpful context but adds no substantive meaning beyond the schema's existing alias documentation.

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 identifies the tool as a beta version of ask_pipeworx and an identical universal router over 5,798 tools, which makes the core purpose clear. It differentiates it from the stable sibling by framing it as the experimental edge, though it still relies somewhat on prior knowledge of what ask_pipeworx itself does.

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 it exactly like ask_pipeworx when you want the newest routing, which gives direct usage guidance. It does not spell out when not to use it or explicitly contrast with ask_pipeworx_grounded, but the current-no-candidate note makes the practical choice clear.

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