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

Discloses state-dependent behavior beyond the annotations: candidate routing improvements are enabled live only when under test, no candidate is currently active, and the tool currently matches ask_pipeworx exactly. It also clarifies that despite being beta, it is a full working router with nothing to fall back to.

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 front-loaded with the key identity and packs current status, usage guidance, comparison behavior, and operational guarantee into three efficient sentences. Each sentence earns its place without redundancy.

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 and high schema coverage, the description covers everything an agent needs: what the tool is, its current active routing state, how it relates to the stable router, and that it is fully operational. The same response shape reference to ask_pipeworx is sufficient despite the lack of an 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 coverage is 100% but every parameter description is only 'Alias for question,' so the input schema provides minimal semantic value. The description adds no per-parameter meaning beyond confirming the same arguments as ask_pipeworx, so the baseline of 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 it is the beta version of ask_pipeworx and an identical universal router routing questions, with the same 5,908 tools, arguments, and response shape. This clearly differentiates it from the stable ask_pipeworx sibling and makes its purpose unmistakable.

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?

Explicitly instructs to use it exactly like ask_pipeworx when the newest routing is desired, and notes results are compared against the stable router to decide merges. It names the alternative and the selection condition, while the 'experimental edge' framing implies when the stable version would be preferred.

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