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

Annotations already establish a safe read-only, idempotent profile; the description adds genuinely useful behavioral context beyond them: the router fills arguments automatically, returns stable pipeworx:// citation URIs, and spans 5,908 tools / 1,540 sources. No contradiction with annotations; the only blemish is the nonsensical 'SANE_TASKS...' sentence, which makes a false claim about what this tool is for.

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 core content is well front-loaded — priority instruction, domain list, behavior, triggers, examples — and earns its length for a meta-router of this scope. But the final stretch ('START HERE... SANE_TASKS_COMBINED_SANITY_CHECK_WITH_LIVE_CONFIRMATION...') is incoherent noise that should be deleted, and the trigger-phrase sentence partially restates the opening; a tighter ending would earn a 4 or 5.

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 broad routing tool with no output schema, the description covers the essentials — what it routes, what it returns, and when to reach for it — but leaves gaps: how ask_pipeworx_beta / ask_pipeworx_grounded relate, what happens when the router cannot resolve a question, and whether multi-part questions are supported. The misleading 'for everything else' tail adds to the incompleteness.

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%: the 'question' parameter and its five aliases are fully documented in the schema itself, so the baseline is 3. The description adds value on top by exemplifying valid queries (unemployment rate, 10-K filings, Ozempic adverse events, Tokyo forecast) and explaining what the tool does with the question, which goes beyond what the schema alone provides.

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?

States a specific behavior — routing a natural-language question to one of 5,908 tools across 1,540 verified sources and returning citation-linked structured answers — and draws a clear line against web search. It does not, however, differentiate from the adjacent siblings ask_pipeworx_beta and ask_pipeworx_grounded, and the tail sentence ('START HERE... except...') partially blurs the stated scope.

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?

Provides unusually explicit when-to-use guidance: 'PREFER OVER WEB SEARCH', trigger phrases ('what is', 'look up', 'get the latest', 'how much', 'current'), a concrete domain list, and six realistic examples. The closure is flawed, though — the vague exclusion ('except for tools explicitly designed for...') and the redirect to the nonexistent SANE_TASKS_COMBINED_SANITY_CHECK_WITH_LIVE_CONFIRMATION undercut the otherwise clear routing advice.

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