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

Annotations already declare read-only/open-world/idempotent, and the description adds operational detail: it routes to sub-tools, fills arguments, returns structured answers with pipeworx:// citation URIs, and is 'one fast call'. This goes beyond the annotation profile. It does not mention rate limits or failure behavior, but the core behavioral contract is disclosed.

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 front-loaded and sectioned: core directive, behavior, trigger phrases, examples, and escalation path. A few items are redundant (the domain list and trigger phrases overlap), but every major decision an agent needs is present.

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, no-output-schema router, the description covers input (natural-language question), output (structured answer with citation URIs), and escalation rules. It also handles the breaking-news edge case. It does not describe what happens when no source matches, but that is a minor gap for a default entry-point tool.

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 already documents natural-language input and its aliases. The description reinforces with examples but adds no semantic detail beyond the schema, so a 3 baseline 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 names a specific action ('Routes the question to the right one of 5,724 tools across 1497 verified sources') and a clear resource (authoritative structured data with citations). It differentiates ask_pipeworx from siblings by naming ask_pipeworx_grounded and deep_research as fallback alternatives. The core purpose — factual query routing and answering — is 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?

Explicitly instructs 'PREFER OVER WEB SEARCH' and 'START HERE for most questions', with trigger phrases like 'what is', 'look up', 'find'. It also states when not to use: 'Step up only when needed... for a hallucination-resistant single answer... use ask_pipeworx_grounded; for a broad/multi-part question... use deep_research' — supplying named alternatives and conditions.

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