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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds beyond that: it discloses the beta/experimental nature, that candidate routing improvements are 'enabled live' when under test, and that results are 'compared against the stable router'. This gives the agent awareness of potential variability and the evaluation context.

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 a single dense paragraph that front-loads the identity (beta of ask_pipeworx) before explaining current state, usage, and safety. Each sentence earns its place, though the accumulation of clauses ('same 5,724 tools, same arguments, same response shape' plus 'candidate routing improvements...') makes it slightly longer than necessary. Still efficient and well-ordered.

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 router tool with no output schema, the description specifies the response shape is identical to ask_pipeworx, covers the current active state ('No candidate is active right now'), and assures it is a fully working router. It does not explain what happens semantically when a candidate is active beyond saying it is 'under test', but given the annotations and schema, an agent has enough information to invoke it correctly.

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 each parameter is documented with descriptions (e.g., 'Alias for question' and 'Your question or request in natural language'). The description mentions 'same arguments' but adds no new parameter-level meaning. Therefore the baseline of 3 is appropriate since the schema handles the heavy lifting.

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 a specific verb and resource: it is a 'beta version of ask_pipeworx' acting as an identical universal router with 'same 5,724 tools, same arguments, same response shape'. It explicitly differentiates itself from the sibling ask_pipeworx by being the experimental edge with candidate routing improvements, so an agent can distinguish it without opening schemas.

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?

Guidance is explicit: 'Use it exactly like ask_pipeworx when you want the newest routing' names the stable sibling as the alternative and gives the condition that selects this tool. It also clarifies what the tool is not ('Falls back to nothing — this IS a full working router'), removing any ambiguity about it being a stub or partial implementation.

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