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

Annotations already declare this as safe, idempotent, and non-destructive, so the description's job was to add behavioral context beyond that. It does so by disclosing that no candidate routing improvement is currently active, that the tool currently matches ask_pipeworx exactly, and that it is a full working router rather than a fallback. This is exactly the kind of state-specific transparency an agent needs.

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 behavior, and every sentence contributes useful context. It is slightly redundant in saying both 'identical universal router' and 'currently matches ask_pipeworx exactly,' but the redundant phrasing reinforces an important point for an experimental tool.

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 single-required-parameter router with full schema coverage and rich annotations, the description is nearly complete. It explains current beta status, usage equivalence, and comparison behavior. The only minor gap is that it references the response shape as 'same' as ask_pipeworx without describing it directly, which is acceptable if the sibling tool's description is available but not 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 description coverage is 100%, with aliases like q, text, input, and prompt fully documented. The description adds no new parameter semantics beyond saying 'same arguments' as ask_pipeworx, so the schema is already carrying the burden adequately.

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 the beta version of ask_pipeworx, a universal router over 5,743 tools, with the same arguments and response shape. It explicitly distinguishes itself from the stable ask_pipeworx by its experimental routing improvements and live-testing behavior.

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 tells the agent exactly when to use this tool: 'Use it exactly like ask_pipeworx when you want the newest routing.' It also explains that results are compared against the stable router to inform merges, providing clear context for choosing this beta tool over its stable sibling.

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