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

Annotations only declare safe/idempotent read behavior, so the description carries the full burden of explaining the rest. It discloses account requirements, paid tier limits, latency (15-60s, up to ~90s), gap[] behavior, contradiction detection, citation URI resolvability, and semantic excerpting. It even warns about empty results for non-catalog topics. This is far beyond annotation coverage and directly shapes caller expectations.

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 and dense, but nearly every sentence earns its place by carrying a distinct operational fact. It is front-loaded with the most critical gate (account requirement and fallback). It would benefit from bulleted structure or section breaks, but it is not padded or repetitive enough to lose more than a point.

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 two parameters, no output schema, and significant behavioral complexity, the description is exceptionally complete. It specifies input expectations, output shape, failure modes, latency, access constraints, and sibling routing. An agent could invoke this tool correctly and interpret its response without any undocumented assumptions.

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 both parameters are already documented. The description adds minor color about depth behaviors (re-angles gaps, chases leads) but mostly restates what the schema's depth description already says. The 'question' parameter gains no new meaning beyond the schema. Baseline 3 is appropriate since the description doesn't significantly extend parameter-level guidance.

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 names a specific verb ('researches') and a precise resource ('Pipeworx's 1497 STRUCTURED data sources'), and explicitly differentiates itself from open-web search and from ask_pipeworx. It states the core mechanism (decomposition, parallel tool routing) and the output (findings packet), so an agent can tell exactly what this tool does and what it is not.

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 routing rules: use ask_pipeworx when signed out, for single lookups, and for breaking/current news; use deep_research for broad/multi-part structured-data questions. It also names the alternative tools directly and explains the conditions for choosing between them. No inference is required.

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