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

Annotations already establish read-only, idempotent, open-world behavior. The description adds valuable behavioral context: it routes to the right underlying tool, fills arguments automatically, and returns stable pipeworx:// citation URIs. It does not mention latency, rate limits, or failure behavior, but those are not critical given the annotation coverage.

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 lengthy but front-loaded with the most important guidance ('PREFER OVER WEB SEARCH') and organized into scope, mechanism, trigger phrases, examples, and a final directive. Every sentence earns its place, though the example list could be trimmed without losing core meaning.

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 complex routing behavior and no output schema, the description sufficiently explains what the tool returns (structured answer with citations) and when to use it. It could add caveats about unsupported question types or citation format details, but for an agent deciding whether to invoke it, the provided context is nearly complete.

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 aliases for the single required question parameter. The description enriches parameter meaning by showing the breadth of acceptable questions and clarifying that natural language queries are expected, along with examples that map directly to the parameter. It does not add syntax details, but those are not needed for a free-text parameter.

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 a natural-language factual query tool that routes to 5,801 tools and returns structured, cited answers. It is specific about the resource (Pipeworx data sources) and action (route and answer), though it does not directly distinguish itself from the ask_pipeworx_beta and ask_pipeworx_grounded sibling tools.

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?

It explicitly instructs to prefer this tool over web search for a wide range of factual/statistical topics, gives trigger phrases, and provides concrete examples. The 'START HERE for most questions' guidance reinforces when to choose it, making the usage context unusually clear.

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