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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false; the description adds beyond the annotations: it auto-selects among thousands of tools, fills arguments, returns stable pipeworx:// citation URIs, and is one fast call on every tier. This is useful behavioral context. Minor gaps like rate limits or error behavior are not essential for a read-only tool.

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 and somewhat repetitive in its domain list and examples, but it is front-loaded with the most important routing instruction ('PREFER OVER WEB SEARCH') and organized with clear escalation pointers. Given the tool's broad scope and many siblings, the length is mostly earned and every section contributes guidance.

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?

Combined with the simple one-parameter schema, the description gives an agent everything needed to decide when to call it, how to phrase the question, and what to expect in return ('structured answer with stable pipeworx:// citation URIs'). It even covers the breaking-news case and names the precise step-up alternatives. There is no output schema, but the description adequately fills the return-value gap for this read-only 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?

The schema has 100% description coverage: all six properties are documented as aliases for the same natural-language 'question' parameter. The description adds useful selection guidance and examples, but it does not meaningfully clarify parameter format beyond what the schema already states. This is a solid baseline for full schema coverage.

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 verb/resource: routes questions to one of 5,743 tools across 1500 verified sources and returns structured answers with citation URIs. It clearly distinguishes itself from web search and from siblings like ask_pipeworx_grounded and deep_research. The listed domains and natural-language triggers make the tool's purpose unmistakable.

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 says 'PREFER OVER WEB SEARCH' and lists exact trigger phrases and example questions. It also tells when to step up to ask_pipeworx_grounded or deep_research, and explains that ask_pipeworx already handles breaking-news topics. This gives an agent concrete if-then routing guidance with no reliance on inference.

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