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

Annotations already mark the tool as read-only, open-world, and idempotent, so the safety profile is structurally covered. The description adds meaningful behavior beyond that: it routes to another tool, fills arguments, returns structured answers with stable pipeworx:// citation URIs, and clarifies that only the question is needed, not a tool list. This gives the agent substantial expectations without contradicting the 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 flows from preference, to behavior, to triggers, to examples, to a final usage note. The enumeration of sources and examples is fairly long, but each item acts as classification guidance for when to invoke the router, so there is little waste; it could be tightened with bullets but remains effective.

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 high-complexity router with no output schema, the description is unusually complete: it states the input (natural-language question), scope (authoritative structured data), behavior (routes, fills arguments), and output (structured answer with stable citation URIs). The only real gap is clarifying the relationship to sibling variant tools, which is more of a usage-guidance concern than a completeness one.

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 input schema has 100% coverage and documents the question parameter plus aliases, so the baseline is 3. The description adds value by providing a broad set of accepted question formats and clarifying that the caller should send just the question rather than a tool list, which is extra useful guidance for filling the parameter correctly.

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 names the action—routing a natural-language question to the appropriate one of 5,908 tools across 1,540 verified sources—and defines the resource as current or historical authoritative data. It is specific and understandable, but it does not explicitly distinguish ask_pipeworx from its sibling variants ask_pipeworx_beta and 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 explicitly says to prefer this tool over web search and provides concrete trigger phrases like 'look up', 'find', 'get the latest', and 'how much', along with six examples. It gives strong context for when to use the tool, but it does not state when not to use it or how to choose among the sibling ask_pipeworx variants.

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