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 beyond those annotations by explaining that the tool routes to a large corpus of tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. It does not cover failure modes or latency, but the annotation coverage lowers the burden.

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 key directive to prefer this tool over web search, then gives domains, trigger phrases, examples, and a closing 'start here' note. It is a bit longer than necessary and repeats the idea of preferring it over search, but every section contributes to how an agent should use the tool.

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 complexity and lack of an output schema, the description does a good job of explaining what to expect: routed answers, argument-filling, and citation URIs. It could still describe error handling, limitations, or interaction with sibling variants, but the provided context is sufficient for an agent to invoke the tool 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?

Schema description coverage is 100%, so the schema already documents all parameters and their aliases. The description reinforces that questions are natural language and gives examples, but it does not add substantial semantic detail beyond what the schema provides, matching the baseline for high schema coverage.

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 a specific purpose: routing natural-language questions to one of 5,908 tools and returning a structured answer with citations. It differentiates primarily from web search rather than from the sibling ask_pipeworx_beta and ask_pipeworx_grounded tools, so it stops short of fully distinguishing among closely related siblings.

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 clear when-to-use guidance: it says to prefer this tool over web search, provides trigger phrases, and includes concrete examples. It does not, however, state when not to use it or how it relates to sibling variants like ask_pipeworx_grounded, so exclusions are missing.

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