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

The description adds meaningful behavior beyond the readOnly/idempotent annotations: it explains the tool is a live-tested router edge, currently has no active candidate, matches ask_pipeworx exactly right now, and has no fallback while still being a full working router. 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 front-loaded with the beta identity and current state, and every sentence contributes context about what the tool is, when to use it, and what it does not do. It is somewhat verbose with exact counts and dates, but none of the sentences are filler.

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 current no-candidate state, equivalence to ask_pipeworx, the comparative purpose of the beta, and the lack of fallback, which is enough for safe invocation. The 'same response shape' note partially compensates for the absent output schema, though a concrete response description would be stronger.

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 question and its aliases. The description only adds that the same arguments as ask_pipeworx are accepted, which is useful but does not materially enrich parameter understanding beyond the schema.

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, states it is an identical universal router with the same tools, arguments, and response shape, and positions it as the experimental edge. This differentiates it from the stable ask_pipeworx and ask_pipeworx_grounded siblings by naming its relation and current equivalence.

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 says to use it exactly like ask_pipeworx when the newest routing is wanted and explains that its results are compared against the stable router to decide what merges. It does not state explicit when-not-to-use scenarios or mention ask_pipeworx_grounded, but the beta framing and 'experimental edge' give clear context.

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