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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description goes well beyond: requires an account and plan tier, explains that gaps[] are explicit and never invented, states that citations are stable and fetchable pipeworx:// URIs, describes semantic excerpting instead of head-truncation, notes contradictions[] for standard/thorough, and gives latency expectations. 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?

Although long, the description is dense and front-loaded. Critical operational context (account required, when to use ask_pipeworx instead, the NOT-open-web distinction) appears first, followed by depth semantics, output packet details, and latency. Every sentence contributes distinct, non-redundant information needed for correct invocation.

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, optionally-paid research tool with no output schema, the description fully compensates: it covers prerequisites, alternatives, return structure (verbatim evidence, confidence, source, fetched_at, citation_uri, hop field, gaps[], contradictions[]), depth options, citation resolvability, and timing. An agent has enough context to decide whether to call it and what to do with the result.

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. The description adds useful depth-parameter nuance beyond the schema: standard re-angles unanswered gaps, thorough chases leads, and latency differs (15-60s, up to ~90s). It also clarifies that the question parameter should be broad/multi-part, reinforcing the schema's own guidance. Minor redundancy, but it does add value.

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 states a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1497 STRUCTURED data sources' in ONE call. It clearly differentiates from ask_pipeworx and other siblings by emphasizing parallel decomposition across 5,724 tools and explicitly saying 'this is NOT open-web search.'

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?

Usage guidance is explicit and actionable: 'Best for broad/multi-part questions over structured data'; 'For a single lookup use ask_pipeworx'; 'For BREAKING or colloquial CURRENT-NEWS ... prefer ask_pipeworx'; and if not signed in, 'use ask_pipeworx instead.' It also names the paid-tier restriction for depth:'thorough'. No ambiguity about when to use this tool vs alternatives.

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