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

The description discloses non-obvious dynamic behavior: candidate routing improvements are 'enabled live whenever one is under test', no candidate is active right now, and this currently matches ask_pipeworx exactly. It also clarifies there is no fallback: 'this IS a full working router, just the experimental edge.' This goes beyond the readOnly/idempotent annotations and helps an agent anticipate changing behavior. No contradiction with annotations.

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 reasonably concise and front-loaded with the beta identity and router scope. Each sentence adds useful context—current candidate status, usage instruction, and no-fallback reassurance. There is minor redundancy between 'identical universal router' and 'matches ask_pipeworx exactly,' but it doesn't obscure the meaning.

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?

Annotations cover safety and idempotence, and the schema covers parameters, but there is no output schema. The description only promises 'same response shape' as ask_pipeworx without specifying what that shape is. For a universal router, more explicit detail about response format and routing behavior would round out the picture, though the alias relationship makes it invocable.

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 all six parameters and their aliases well. The description adds only 'same arguments' without explaining question semantics, routing behavior, or expected phrasing. This meets the baseline but provides no additional parameter insight.

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 frames the tool as 'Beta version of ask_pipeworx: identical universal router (same 5,724 tools, same arguments, same response shape)', making it clear this is an experimental question-routing tool. It distinguishes itself from the stable sibling by its beta status, but the core 'ask a question and route it' action is implicit and relies on prior understanding of ask_pipeworx.

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 explicitly says 'Use it exactly like ask_pipeworx when you want the newest routing', giving a clear condition for selection. It also explains the comparison role: 'results are compared against the stable router to decide what merges.' It doesn't state when not to use it, but the experimental/beta framing makes the exclusion inferable.

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