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

Annotations already carry readOnlyHint/openWorldHint/idempotentHint, and the description adds substantial context beyond them: account-tier auth requirements, 15-90s latency expectations, never-invented-data guarantee with explicit gaps[], semantic excerpting (vs head-truncation), citation_uri resolvability, and contradictions[] behavior per depth level. The openWorldHint is reinforced by the caveat that deep_research returns empty gaps[] for non-catalog topics. No contradiction with 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?

Nearly every sentence carries distinct operational value — account tiers, timing, return format, citation resolution, hops, contradictions. It is long but front-loaded with the most critical gate (ACCOUNT REQUIRED) before the capability pitch. Slightly dense/run-on in places, but for a tool with this much nuance (tiers, alternatives, multi-hop behavior) the length is largely earned.

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?

No output schema exists, so the description must carry the return contract — it does, fully: findings packet with verbatim evidence, confidence, source, fetched_at, pipeworx:// citations, gaps[], hop field, citation_uri, and contradictions[]. Combined with auth, timing, alternatives, and depth semantics, nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3. The description adds meaningful value beyond the schema for the depth parameter: it documents the paid-plan requirement for 'thorough', distinguishes gap-recovery vs. lead-chasing hops, and explains the contradictions[] scan per level. Question is adequately covered by both schema and description.

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?

"Grounded multi-source research across Pipeworx's 1497 STRUCTURED data sources...in ONE call" states a specific verb, resource, and scope, and explicitly asserts "this is NOT open-web search." It names sibling tools it must be distinguished from (ask_pipeworx, search) and gives concrete use cases, so an agent can tell it apart without opening the schema.

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?

Provides explicit when-to-use guidance ("Best for broad/multi-part questions over structured data") and explicit when-not-to-use with named alternatives: single lookups → ask_pipeworx, breaking/colloquial current news → ask_pipeworx. Also routes unsigned-in users to ask_pipeworx upfront, which is a decisive selection criterion.

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