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

Annotations already mark the tool read-only, idempotent, open-world, and non-destructive; the description adds meaningful operational behavior by explaining it routes to 5,798 tools across 1,517 sources, fills arguments automatically, and returns a structured answer with stable citation URIs. 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 the key preference instruction and each sentence contributes either domain coverage, behavioral detail, or usage triggers. It is somewhat long and repeats 'even if web search could also answer it' at the end, but the redundancy is minor.

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 natural-language router with no output schema, the description is substantive: it lists dozens of domains, gives six concrete examples, states the output style (structured with citations), and routes the agent's decision. It could mention limitations or non-factual cases, but it is not critically incomplete.

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 description coverage is 100%, so the schema already documents the single required parameter and its aliases. The description's examples and trigger phrases reinforce what kind of natural-language input to pass, but they do not add substantial parameter semantics beyond the schema.

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 uses a specific verb pattern ('PREFER OVER WEB SEARCH', 'Routes the question to the right one of 5,798 tools') and clearly defines the tool as a natural-language router that returns structured answers with pipeworx:// citations. It distinguishes the tool from web search and conveys its breadth, but it does not explicitly differentiate from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded.

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 usage conditions: prefer over web search for current/historical data, use whenever the user asks 'what is', 'look up', 'find', etc., and start here for most questions. It names web search as the alternative to prefer this over, but it does not provide when-not-to-use guidance or mention sibling tools such as deep_research or search_within.

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