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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds meaningful context: it explains the tool is currently identical to ask_pipeworx, that no candidate routing improvement is active, and that it falls back to nothing (a full working router). This goes beyond annotations by disclosing current experimental state and comparison behavior.

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 compact and front-loaded with the key identity ('Beta version... identical universal router'), followed by current state and usage guidance. The 5,798 tools detail and retirement date add some specificity but also slightly dilute the core message. Overall efficient and well-organized.

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 tool is a beta mirror of ask_pipeworx with no output schema, the description adequately explains current behavior, that it is fully functional, and how it differs from the stable tool. It does not describe the response shape explicitly, but says it is the same as ask_pipeworx, which is sufficient for agent invocation. Minor gap: no explanation of how to distinguish outputs or what 'candidate routing improvement' results look like.

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 description coverage is 100%, so the schema already documents the question parameter and its aliases. The description reinforces that arguments are the same as ask_pipeworx ('same arguments'), which is useful but not detailed. Baseline 3 is appropriate because the schema carries the parameter documentation burden and the description adds only marginal context.

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 variant of ask_pipeworx, a universal router with the same tools and arguments. It states 'identical universal router' and 'use it exactly like ask_pipeworx', which gives a specific verb and resource. It distinguishes from ask_pipeworx by noting it's the experimental edge, but doesn't fully detail what 'candidate routing improvements' means.

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 clearly frames when to use this beta variant, though it does not explicitly list exclusions or alternative conditions beyond naming ask_pipeworx as the stable counterpart.

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