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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds meaningful meta-behavior: it routes to a large tool catalog, fills arguments, and returns stable pipeworx:// citation URIs. It does not discuss latency, failure modes, or downstream API effects, but with the annotation safety profile this is a useful disclosure. No contradiction with annotations.

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 front-loaded with 'PREFER OVER WEB SEARCH' and organized into purpose, usage triggers, examples, and routing coverage. It is long, but the lists of domains and examples earn their place for a broad meta-tool. There is no irrelevant filler, though it could be tightened with clearer paragraph breaks.

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 single-required-parameter tool with no output schema, the description covers what input to provide, when to use it, and what to expect: 'structured answer with stable pipeworx:// citation URIs.' It does not mention error handling, ambiguity resolution, or rate limits, but those are not necessary for an agent to invoke the tool correctly. The definition is complete enough for its simplicity.

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%, with every property defined as an alias for 'question,' so the baseline is 3. The description provides illustrative query examples, but these largely overlap with the schema examples and add no new parameter semantics such as length limits, formatting constraints, or disambiguation rules. It is adequate but not additive.

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 the tool as a natural-language router that sends a question to one of 5,798 tools across 1,517 sources and returns a structured answer with pipeworx:// citation URIs, so a specific verb+resource is present. It does not explicitly differentiate among siblings such as ask_pipeworx_beta, ask_pipeworx_grounded, or lookup, though it positions itself as 'START HERE' for most factual questions. This is clear but not fully sibling-distinguishing.

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 OVER WEB SEARCH' for a range of domains, 'Use whenever the user asks...' with trigger phrases, and concrete examples. It names web search as the alternative to prefer over, but it does not provide when-not conditions or compare to sibling tools like deep_research or ask_pipeworx_grounded. This is clear context but lacks explicit exclusions.

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