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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses the beta status, live candidate routing, current inactive state, and that results are compared against the stable router to decide merges. The line 'Falls back to nothing — this IS a full working router' adds reassurance about the tool's completeness. No contradiction with the 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?

Three sentences, each earning its place: the beta identity and what is identical, the current state with no active candidate, and usage guidance plus a reassurance about reliability. The essential 'beta version... identical universal router' is front-loaded. It is slightly dense but remains efficient.

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 tool's relationship to ask_pipeworx, its experimental nature, current behavior, and usage. There is no output schema, but the description points to 'same response shape' as ask_pipeworx, which is an adequate pointer if the agent inspects that sibling. It does not state the concrete response format, but the reference is reasonable given the ecosystem context.

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%, and the provided schema documents aliases as 'Alias for question', so the baseline is 3. The description adds only 'same arguments' as ask_pipeworx, which is redundant with the schema and does not explain the expected content of the question. It neither compensates for nor clarifies the missing explicit 'question' property in the visible schema snippet.

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 states this is a 'beta version of ask_pipeworx' and an 'identical universal router (same 5,738 tools, same arguments, same response shape)', clearly identifying it as a routing/answering tool. It distinguishes itself as the experimental edge from the stable ask_pipeworx sibling, though full clarity relies on the reader knowing what ask_pipeworx does.

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', giving a clear when-to-use condition plus a reference to the stable alternative. It also notes that no candidate is currently active, so it currently matches ask_pipeworx exactly, which helps an agent decide it's safe to call. It does not address ask_pipeworx_grounded, but the guidance is sufficient for choosing between the stable and beta variants.

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