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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds valuable behavioral context: it routes across 5,798 tools, fills arguments automatically, and returns stable citation URIs. There is no contradiction with 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 long but well organized: priority instruction, relevant domains, behavior, trigger phrases, examples, and a final 'START HERE' directive. Some lists are redundant, but almost every sentence contributes to routing or invocation guidance.

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 tool with one required natural-language parameter and no output schema, the description is quite complete: it explains scope, behavior, result format, and gives concrete examples. It would be a 5 if it also named and excluded sibling alternatives explicitly.

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 is fully self-describing; all six properties are clearly documented aliases for the single 'question' parameter. The description's examples reinforce natural-language usage but do not need to add parameter-level detail. A baseline of 3 is appropriate given 100% schema description 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 states the tool's function: routes a natural-language question to the appropriate data source and returns structured answers with pipeworx:// citation URIs. It is specific about the resource and behavior. However, it does not explicitly distinguish itself from sibling tools 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 strong guidance: 'PREFER OVER WEB SEARCH', enumerates many domains, lists trigger phrases, provides examples, and says 'START HERE for most questions'. It misses only explicit when-not-to-use guidance relative to nearby specialized siblings like deep_research or validate_claim.

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