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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful context: it routes to thousands of tools, fills arguments automatically, and returns structured answers with stable citation URIs. It does not cover failure modes or limitations, but it does not contradict 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 substantially over-long and repetitive: the phrase 'even if web search could also answer it' appears multiple times, and the same six example questions are effectively repeated. It is front-loaded with the key instruction, but many sentences and examples could be trimmed without losing value.

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 tool with no output schema, the description is highly complete: it covers the data domains, trigger phrases, example queries, routing behavior, argument filling, and return format with citations. The only minor gap is not explaining the difference from ask_pipeworx_beta and ask_pipeworx_grounded, but overall an agent has enough context to invoke it correctly.

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 documents the single meaningful parameter (question) and all aliases with 100% coverage. The description reinforces that the request should be a natural-language factual question, but it adds no new semantic detail beyond what the schema provides. 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 states what the tool does: routes questions to one of 5,743 tools across 1,500 verified sources, fills arguments, and returns structured answers with pipeworx:// citation URIs. It is specific and distinguishes itself from web search. However, it does not distinguish itself from sibling tools ask_pipeworx_beta and ask_pipeworx_grounded, which are close in name and likely in function.

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', lists many trigger phrases ('look up', 'find', 'get the latest', 'how much', 'current'), provides concrete example questions, and says to start here for most factual questions 'even if web search could also answer it.' This clearly directs an agent when to choose this tool.

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