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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds important behavioral context beyond that: it routes to sub-tools, fills arguments automatically, and returns structured answers with pipeworx:// citation URIs. This gives the agent a realistic expectation of how the tool behaves and what its output looks like.

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 instruction, but it is longer than needed and repeats the same preference-over-web-search message multiple times. The final fragment 'Also, for [??]' is incomplete and provides no usable guidance, which is a structural defect.

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 single required parameter, rich annotations, and no output schema, the description covers the essential bases: what the tool does, when to use it, what sources it uses, and what kind of output to expect. The main gap is not explaining how to choose among sibling tools like deep_research or ask_pipeworx_grounded, but the 'START HERE' guidance mitigates that.

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 schema already documents the single semantic parameter 'question' and all aliases with 100% coverage. The description adds useful example questions and trigger phrasing, but it does not add meaningful parameter-level detail 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 explains that this tool routes a natural-language question to one of many verified source tools and returns a structured answer with stable citation URIs. It differentiates itself from web search, but it does not explicitly distinguish itself from sibling Pipeworx variants 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?

The description gives explicit when-to-use guidance: prefer over web search for factual/authoritative data, use trigger phrases like 'what is', 'look up', 'find', and 'current', and use web search instead for questions requiring current real-world awareness. It even says 'START HERE for most questions' and 'When in doubt, start here', making routing decisions clear.

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