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

Annotations already signal a safe, read-only, open-world operation, and the description adds real behavioral context: it routes to one of 5,798 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// 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 long but information-dense and front-loaded with the most important instruction to prefer this tool over web search. The domain list and examples earn their place, though the closing START HERE somewhat repeats the earlier preference guidance.

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 broad, one-parameter query router with no output schema, the description covers scope, trigger conditions, examples, routing behavior, and citation return format. It is complete enough to invoke correctly, though it does not describe the answer structure in detail or differentiate the ask_pipeworx sibling variants.

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% and the single meaningful parameter (question) plus its aliases are fully documented in the input schema. The description adds examples and trigger phrases, but it does not need to explain parameter syntax beyond what the schema already provides.

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 ask_pipeworx as a natural-language question router over authoritative structured data and lists concrete domains. It distinguishes from web search but does not distinguish it from sibling tools 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?

It gives explicit when-to-use guidance: prefer over web search for factual, current, or historical questions, with trigger phrases and examples, and concludes START HERE for most questions. It does not, however, say when to choose the sibling ask_pipeworx variants instead.

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