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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds meaningful behavioral context on top: it reveals that the tool is an aggregator/router that fills arguments and emits stable pipeworx:// citation URIs. It does not, however, disclose potential failure modes, coverage limits, or latency.

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 opening is strong and front-loaded, but the description repeats the 'START HERE for most questions — even if web search could also answer it. Examples: ...' block verbatim at least twice, adding needless length and making the definition feel corrupted. It should stop after the first set of examples.

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 simple one-required-parameter tool, the description covers the core use case, expected behavior, and output characteristic (structured answer with citations). There is no output schema, so a little more detail on the shape of the structured response would be ideal, but the description is still sufficiently complete for an agent to select and invoke the tool.

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?

With 100% schema coverage, the schema already documents all six parameters (question plus five aliases) as natural-language strings. The description reinforces the intended input with trigger phrases and examples, but adds little parameter-level meaning beyond that baseline.

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 verb and resource: it routes natural-language questions to one of 5,743 tools across 1,500 verified sources and returns structured answers with citation URIs. It also distinguishes itself from generic web search, but it does not explicitly differentiate from sibling tools such as ask_pipeworx_beta or ask_pipeworx_grounded, so it stops short of a 5.

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...' and 'Use whenever the user asks ... any factual question', reinforced by concrete examples and 'START HERE for most questions'. It provides no when-not-to-use guidance or named alternatives among the sibling tools, so it lacks full exclusionary context.

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