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

Annotations already declare read-only, open-world, idempotent behavior. The description adds operational traits not present there: the tool automatically fills arguments, routes to thousands of sources, and returns a structured answer with stable pipeworx:// citation URIs. It also states it is the default starting point, which is useful behavioral context. No contradiction with annotations is present.

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 overlong and contains redundant guidance, including a garbled section that appears to duplicate the 'START HERE' advice and alternative-tool routing. While front-loaded with 'PREFER OVER WEB SEARCH', the subsequent list of domains, examples, and repeated alternatives makes it hard to scan. This is over-specification rather than concise precision.

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 complex aggregator with no output schema, the description provides the necessary operational details: what it returns (structured answer with citation URIs), what kinds of questions it handles, and which siblings to step up to for special cases. It also tells the agent this is the default starting point, which is exactly the contextual information needed for correct routing. It could mention limitations or failure modes, but nothing critical is missing for selecting and invoking it.

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 description coverage, the baseline is 3, but the description earns a 4 by clarifying that the only thing the agent must supply is a natural-language question and that the tool itself 'fills arguments'. The detailed examples ('current US unemployment rate', 'Apple's latest 10-K', 'active clinical trials for GLP-1') convey acceptable input phrasing beyond the schema's generic description. It reinforces the semantic that any factual question works, not just a specific parameter format.

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 opens by framing ask_pipeworx as the tool to prefer over web search for factual/structured-data questions and defines its mechanism: routing to 5,798 tools across 1,517 verified sources, filling arguments, and returning cited answers. It clearly differentiates from siblings by naming ask_pipeworx_grounded, deep_research, validate_claim, and compare_entities as purpose-specific alternatives. The verb-resource pair is unambiguous: answer a question by fetching from verified sources with citations.

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?

Explicitly lists trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current') and says to use the tool even when web search could also answer. It then provides explicit alternatives with exact conditions: ask_pipeworx_grounded for citation-verified single answers, deep_research for multi-step reports, validate_claim for quick claim checks, and compare_entities for side-by-side comparison. This is the kind of when/when-not guidance the dimension requires.

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