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

Annotations already declare readOnly/openWorld/idempotent/non-destructive behavior, and the description adds useful behavioral context: it fills arguments, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and is described as one fast call. It also implies a limitation by recommending ask_pipeworx_grounded for verbatim evidence and confidence.

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 longer than average, but it is front-loaded with the 'PREFER OVER WEB SEARCH' directive and each section serves a routing purpose: scope, triggers, examples, and alternatives. It is slightly wordy and repetitive, so it does not earn a 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 default router with no output schema, the description covers when to use it, what it returns, how it handles live news, and which sibling to escalate to. Nothing an agent needs to decide whether to call it, or what question to pass, is missing.

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 all six parameters are aliases of 'question', so the schema fully documents the parameter surface. The description provides example questions but does not add semantic meaning beyond what the schema already supplies; baseline 3 is appropriate.

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 a broad routing/search purpose: it 'routes the question to the right one of 5,743 tools' and returns structured answers with citations. It also distinguishes itself from web search and from sibling tools like ask_pipeworx_grounded and deep_research.

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 explicit trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current') and says to prefer this tool over web search. It also states exactly when to step up: use ask_pipeworx_grounded for hallucination-resistant answers and deep_research for broad/multi-part questions.

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