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

Annotations already mark readOnly/openWorld/idempotent, and the description adds rich behavioral detail: parallel decomposition, findings packet contents, gaps[] and contradictions[], never-invented guarantee, citation URI fetchability semantics, semantic excerpting behavior, and latency expectations. It even discloses quirks like the hop/citation_uri field and the head-truncation avoidance. No contradictions 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?

The description is information-dense and front-loaded with the critical account requirement, but it is very long and somewhat stream-of-consciousness, mixing warnings, mechanics, return format, and latency in one block. Every sentence earns its place, but the single-paragraph structure makes it harder to parse. Slightly over-long for what it needs to convey.

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 two-parameter, no-output-schema tool, the description covers account requirements, alternative tools, what output to expect, latency, and edge-case behavior (gaps, contradictions, semantic excerpting). It does not provide a sample findings packet, but given no output schema exists, the detailed prose description of the packet largely compensates. Missing a consolidated quick-reference of the depth tiers, though the schema covers that.

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 schema already documents both parameters, including the depth enum values. The description adds context about what standard/thorough add (gap-recovery hop, contradictions scan) and quick default, but doesn't significantly go beyond the schema's parameter descriptions. Baseline 3 is appropriate.

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 (research), resource (Pipeworx's 1517 structured data sources via 5,798 tools), and explicitly differentiates from open-web search, ask_pipeworx, and single lookups. Naming siblings and the NOT-open-web distinction makes it unmistakable.

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 says when to use (broad/multi-part questions over structured data), gives concrete examples, and says when not to (single lookup → ask_pipeworx; not signed in → ask_pipeworx). Also notes which depth is paid. This is textbook routing guidance.

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