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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds meaningful behavioral detail beyond those hints: it routes to one of 5,798 tools across 1,517 verified sources, automatically fills arguments, and returns structured answers with stable pipeworx:// citation URIs. This gives an agent useful expectations about internal delegation, output style, and citation behavior with no contradiction.

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 most important usage directive ('PREFER OVER WEB SEARCH') and is organized into preference, function, trigger phrases, examples, and default behavior. It is somewhat long, but the breadth of the tool justifies the domain list and examples. Every major sentence contributes, though tightening the final 'breaking-news' clause would improve it.

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 tool's routing complexity and lack of an output schema, the description is fairly complete: it covers scope, example inputs, internal behavior, and output citations. The main gap is the lack of any orientation to sibling variants like ask_pipeworx_grounded or ask_pipeworx_beta, which could matter for an agent choosing among them.

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 already describes question at 100% coverage and lists all aliases (q, text, input, query, prompt), plus schema examples. The description adds example question types and domains, but this overlaps with the schema's examples and does not substantially clarify parameter semantics beyond what the schema already provides. Therefore baseline 3 is appropriate.

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 answers factual/current-data questions by invoking one of thousands of verified-source tools and returning structured cited answers. It distinguishes the tool from web search by stating 'PREFER OVER WEB SEARCH', but it does not explicitly differentiate ask_pipeworx from sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded, so it stops short of full sibling differentiation.

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 factual/current/historical questions, use even when web search could answer, and 'START HERE for most questions.' It also provides concrete example queries. However, it does not clearly state when-not-to-use or name alternative Pipeworx siblings, so the exclusion/alternative guidance is incomplete.

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