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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description adds crucial behavioral context: no candidate is currently active, so it currently matches ask_pipeworx exactly, and it 'falls back to nothing' because it is a full working router, not a thin wrapper. This clarifies the live experimental state and the absence of fallback 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 somewhat verbose with details like 'same 5,798 tools, same arguments, same response shape,' but each sentence earns its place by clarifying the beta status, current inactive candidate state, usage instruction, and non-fallback guarantee. It is front-loaded with the core purpose and remains readable.

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?

The description covers the beta status, current behavior, usage, and comparison role well. There is no output schema, but the description compensates by noting the 'same response shape' as ask_pipeworx. Missing explicit rate limits, authentication, or response format details, but for a router that delegates to an existing stable counterpart, this is reasonably complete.

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 fully documents the aliases and the required question parameter. The description only says 'same arguments' without elaborating on parameter semantics. This is adequate but adds no value beyond the schema, so the baseline of 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 clearly identifies this as a beta version of ask_pipeworx: 'identical universal router (same 5,798 tools, same arguments, same response shape) with candidate routing improvements enabled live.' It distinguishes itself from the stable ask_pipeworx and states its experimental role. The purpose is specific and immediately understandable.

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 'Use it exactly like ask_pipeworx when you want the newest routing,' which gives a clear usage condition. It also explains that results are compared against the stable router to inform merges. However, it does not state when not to use it or mention alternatives like ask_pipeworx_grounded, so it stops short of full exclusion guidance.

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