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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond annotations by explaining that candidate routing improvements may be active, that the tool is an experimental edge, and that it is a full working router with no fallback.

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 but not bloated; each sentence contributes either identity, current state, or usage guidance. It front-loads the key beta designation and parity with ask_pipeworx, though the date of the last retired candidate adds minor detail that is useful but not strictly necessary.

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 that this is a router with high complexity and no output schema, the description covers identity, parity with ask_pipeworx, the experimental nature, current candidate status, and usage guidance. It says the response shape matches ask_pipeworx, which is sufficient for a beta variant, though a brief example or explicit return description would make it fully self-contained.

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 all six parameters are documented in the schema as aliases for 'question.' The description only mentions 'same arguments' and does not add parameter-level meaning, but this is acceptable because the schema fully covers all aliases and the required field.

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 and explains it is a universal router with the same 5,767 tools and same response shape. It distinguishes itself from the stable ask_pipeworx sibling by emphasizing the experimental routing improvements, though it does not explicitly contrast it with ask_pipeworx_grounded.

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 'exactly like ask_pipeworx when you want the newest routing' and notes that results are compared against the stable router. It gives clear context about current behavior matching ask_pipeworx because no candidate is active, but it does not state when not to use it or mention alternatives beyond the stable router.

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