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

Annotations already convey readOnly, idempotent, open world, non-destructive, so the safety profile is covered. The description then adds substantial behavioral context: parallel decomposition across 5,798 tools, findings packet structure (evidence, confidence, source, fetched_at, pipeworx:// citation), explicit gaps[] for unanswered facets, never-invented behavior, excerpting rather than head-truncation, latency expectations, and depth-dependent contradiction scanning. It also discloses that citation_uri is present only when the source emits a fetchable URI.

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?

Front-loaded with the most decision-critical info: account requirement and the unsigned-user alternative. Every sentence carries signal, but the description is long and dense, with somewhat distracting parenthetical wordplay ('compare X and Y's regulatory + financial exposure') embedded in a long run-on. Still, the density is largely earned given the tool's complexity.

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 research tool with no output schema, the description compensates thoroughly: it explains return structure, citation semantics, gap handling, latency, depth tiers, pricing gating, and when to use the sibling instead. Nothing an agent needs to decide whether to call this and what to expect 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 schema already documents both parameters well. The description adds actionable semantics beyond the schema: depth:'quick' is described as single hop, 'standard' and 'thorough' add gap-recovery/contradiction passes, and 'thorough' requires a paid plan. The question parameter's natural-language / multi-part acceptance is also reinforced. Slight deduction because the description does not enumerate the 5,798 tools or explain how facets are chosen, but the schema plus description is more than sufficient for invocation.

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 1517 structured data sources in one call — and explicitly distinguishes itself from open-web search. It also names the primary alternative (ask_pipeworx) and the condition for choosing it, which anchors its purpose among 33 siblings.

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 gives concrete example questions. It also states when NOT to use it (single lookup → use ask_pipeworx) and flags the account prerequisite with the alternative for unsigned users. This is unusually complete.

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