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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: live candidate routing improvements, current equivalence to ask_pipeworx, comparison against the stable router for merge decisions, and the explicit warning that it does not fall back to anything. No contradiction exists.

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 four sentences and front-loaded with the core identity and version relationship. It is appropriately sized for a nuanced experimental tool, though 'identical', 'same', and 'exactly' are slightly repetitive.

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 natural-language router, the description covers experimental status, equivalence to the stable sibling, current inactive-candidate state, and fallback behavior. The response shape is referred to as identical to ask_pipeworx; while no output schema exists, an agent knows the tool is full working and invocable with a question.

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 fully documents the single logical parameter 'question' plus its five aliases. The description only says 'same arguments' and does not add parameter-specific meaning beyond the schema, so the baseline 3 applies.

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 a specific role: a beta universal router identical to ask_pipeworx, forwarding natural-language questions to one of 5,724 tools with the same arguments and response shape. It also clearly marks this as the experimental edge of the stable sibling, making the distinction between ask_pipeworx_beta and ask_pipeworx explicit.

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 gives an explicit usage condition: 'Use it exactly like ask_pipeworx when you want the newest routing.' It also explains the current no-active-candidate state, confirms the tool is a fully working router rather than a fallback, and signals that results are compared with the stable router, which frames when this should be chosen.

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