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

The description goes well beyond the readOnly/openWorld/idempotent annotations by disclosing that routing candidates may be live under test, that results are compared against the stable router, and that it 'Falls back to nothing — this IS a full working router.' This prevents the agent from treating it as a stub or assuming purely stable behavior. No contradiction with annotations exists.

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 dense yet purposeful, front-loading the beta relationship and using each sentence to add current status, experimental intent, or usage direction. The parenthetical about the retired candidate and the explicit 'falls back to nothing' clarification are slightly verbose but useful for setting agent expectations. Overall it is well-structured and earns its length.

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?

Given the rich annotations and the reference to ask_pipeworx, the description covers current behavior, relationship to the stable router, and intended usage. It does not concretely define the response shape, but 'same response shape' is sufficient when the sibling is known. For a broad universal router, 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?

Input schema coverage is 100% and every parameter, including aliases, has a description, so the schema already carries the semantic load. The tool description only restates that arguments match ask_pipeworx and adds no new per-parameter meaning. This meets the baseline for high schema coverage but adds nothing extra.

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 the beta variant of ask_pipeworx and a universal router with the same 5,743 tools, arguments, and response shape. It also distinguishes itself from the stable ask_pipeworx by its experimental routing candidate. However, it leans on the sibling's implied meaning rather than defining the core action in fully plain operational terms.

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 to 'Use it exactly like ask_pipeworx when you want the newest routing' and contrasts the beta router with the stable router whose results are compared for merge decisions. It also discloses the current no-candidate state, so an agent knows it currently behaves identically to ask_pipeworx. This is explicit usage guidance with a named alternative.

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