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

Annotations already mark the tool read-only and idempotent, and the description richly supplements them: it discloses the account/paid-plan requirement, the parallel decomposition into 5,724 tools, the findings-packet shape (verbatim evidence, confidence, source, fetched_at, pipeworx:// citation), the gaps[] never-invented behavior, contradictions[], semantic excerpting, and 15-90s latency. It even warns that current-news topics yield mostly empty gaps[].

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 a dense paragraph, but nearly every sentence earns its place by carrying a distinct fact the agent needs. It is front-loaded with the account prerequisite and the key alternative (ask_pipeworx) before describing mechanics. It could be more skimmable with bullets or section headers, but it is not padded.

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?

Despite having no output schema, the description fully describes what the agent will receive: findings packets with verbatim evidence, confidence, source, fetched_at, citation_uri, hop field, gaps[], and contradictions[]. It also covers prerequisites, alternatives, latency, and failure behavior for unsupported topics. Nothing critical is missing for a tool this complex.

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 the baseline is 3, but the description adds operational meaning beyond the schema: it notes 'depth:"thorough" needs a paid plan', adds expected latency by depth (15-60s, thorough up to ~90s), and clarifies that the question parameter should be broad/multi-part because 'decomposition is the point'. This is modest but real value beyond the schema.

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?

States a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1497 STRUCTURED data sources' in ONE call, and explicitly distinguishes itself from open-web search ('this is NOT open-web search'). It also differentiates from ask_pipeworx by positioning itself as the multi-facet parallel-research tool rather than a single-lookup tool.

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 clear exclusions: 'For a single lookup use ask_pipeworx' and 'For BREAKING or colloquial CURRENT-NEWS... prefer ask_pipeworx'. Also gives a concrete prerequisite condition: if not signed in, use ask_pipeworx instead.

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