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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds useful behavioral detail: it routes the question among thousands of tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. This goes beyond the annotation hints, though it does not discuss failure modes, rate limits, or response formatting edge cases.

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 contains a severe repetition problem: the 'Use whenever... Examples... START HERE' block is repeated many times nearly verbatim. While the opening is front-loaded, the unnecessary repetition makes the definition bloated and harder for an agent to parse efficiently.

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 that there is no output schema, the description does well to specify that the result is a structured answer with stable citation URIs. It covers supported domains, example queries, and the routing nature of the tool; the main quality issue is redundancy, not missing critical selection or invocation information.

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%: all six parameters are documented as aliases for the free-text question. The description adds the general idea of filling arguments internally, but it does not add parameter-level meaning beyond the schema, so the baseline score of 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 ask_pipeworx as a natural-language question router that queries authoritative data sources and returns cited structured answers. It is specific about the resource and behavior, but it does not explicitly differentiate among sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded, so it falls short of full sibling distinction.

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 strong usage guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', concrete trigger phrases such as 'what is', 'look up', and 'current', plus a broad list of supported domains and example questions. It even addresses the alternative by saying this tool should be used even when web search could also answer.

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