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 valuable behavioral context: it routes to other tools, fills arguments, returns pipeworx:// citation URIs, and notes it works on every tier with one fast call. No contradictions with annotations, and it goes beyond what annotations provide.

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 information-dense, front-loading the 'PREFER OVER WEB SEARCH' guidance and providing examples and alternatives. It earns its length by covering usage scope, routing behavior, and sibling distinctions, though it could be slightly 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?

Given the tool's complexity as a routing meta-tool, the description is remarkably complete: it covers when to use, what it does, how it works, what it returns, and how it differs from siblings. No gaps for an agent to call it correctly, especially since annotations cover the safety profile.

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% coverage with each alias parameter described, and the primary 'question' parameter explains it accepts multiple aliases. The tool description doesn't add further parameter semantics beyond what the schema already documents, so a baseline 3 is appropriate since the schema carries the load.

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 function: it routes natural-language questions to one of 5,798 tools across 1,517 verified sources, fills arguments, and returns structured answers with citation URIs. It distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by positioning itself as the default fast entry point, and lists specific domains it covers.

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 to prefer this over web search for factual data questions, lists trigger phrases like 'what is' and 'look up', provides concrete examples, and directs when to step up to ask_pipeworx_grounded or deep_research. This is exemplary usage guidance with clear when-to-use and when-not-to-use conditions.

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