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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses dynamic behavior: candidate routing improvements can be enabled or retired, none is active now, and the tool currently matches the stable router exactly. It also explicitly warns there is no fallback, which prevents an agent from assuming a degraded beta path.

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 compact and front-loaded with the core purpose in the first sentence. Later sentences add valuable operational details (current candidate status, no fallback), though the parenthetical retired-date detail is slightly more than necessary.

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 universal router with no output schema, the description compensates by stating the response shape matches ask_pipeworx exactly and by referencing the 5,908 tools. It leaves the actual routing/response details to ask_pipeworx, but this is acceptable given the sibling tool and 100% schema coverage.

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 coverage is 100% and each of the six parameters has an alias description, so the schema already carries the parameter semantics. The description only adds that arguments are identical to ask_pipeworx, which is useful confirmation but not additional meaning 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 identifies a specific verb-use (ask) and resource (universal router for 5,908 tools) and clearly distinguishes this beta from its stable sibling ask_pipeworx by mentioning experimental routing improvements. The phrase 'identical universal router' plus the beta framing makes its role unambiguous.

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 gives an explicit use condition: 'Use it exactly like ask_pipeworx when you want the newest routing.' It also explains the current state where it matches ask_pipeworx exactly. It does not explicitly tell the agent to prefer ask_pipeworx for stable/production use, but the beta distinction makes that implication clear enough.

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