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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description's added value is the routing behavior, the 5,743-tool scope, and the promise of stable citation URIs. This contextualizes what actually happens when the tool is invoked, though it does not discuss limitations like latency or routing failures.

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 long but logically organized: preference statement, core mechanism, usage patterns, examples, and alternatives. It is front-loaded with the most important guidance. Some redundancy exists in the long list of trigger phrases and examples, which could be trimmed without losing value.

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 complex meta-routing tool with no output schema, the description covers the essential context: what types of questions to route here, what the tool returns (structured answer with citation URIs), how to phrase input, and when to use other tools instead. Nothing critical is missing for an agent to select and 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 coverage is 100%: the schema fully documents the single required 'question' parameter, its natural-language semantics, and all aliases (query, q, prompt, text, input). The description adds query examples and domain coverage, but no parameter-specific meaning beyond what the schema already provides, so 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 states the tool's core function: it routes a natural-language question to the right one of 5,743 tools across 1,500 verified sources, fills arguments, and returns a structured answer with pipeworx:// citation URIs. This distinguishes it from web search and from siblings like ask_pipeworx_grounded and deep_research, which are explicitly named.

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 when-to-use guidance: prefer it over web search for factual/current/structured-data questions, and 'start here for most questions.' It also names alternatives and the conditions for escalating: ask_pipeworx_grounded for a single hallucination-resistant answer with evidence, 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.