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

Beyond the readOnlyHint, openWorldHint, and idempotentHint annotations, the description reveals significant behavioral detail: account sign-in requirements, paid depth tier, parallel facet decomposition, gap reporting, never-invented findings, fetchable citation_uri conditions, contradiction scans, semantic excerpting of large records, and expected latency. No contradiction exists between the description and the 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 long but each sentence carries substantive information: auth, alternative tools, core mechanism, output format, gaps, citations, contradictions, latency. It front-loads the most decision-critical facts (account required, alternative tool). It loses a point for some structural jumping between depth mechanics and return-format details, and for partially repeating the schema's depth enumeration.

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?

Given the tool's complexity and the absence of an output schema, the description is unusually complete. It explains what the findings packet contains, how gaps are handled, when citations are resolvable, how contradictions appear, what latency to expect, and which alternatives to use. An agent has enough context to select and invoke this tool correctly.

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 meaningful context beyond the schema by clarifying the account/paid-plan implication of depth and reinforcing the natural-language, multi-part nature of question. However, much of the depth behavior is already documented in the schema, so the added semantic value is moderate rather than transformative.

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 action and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' in one call. It clearly distinguishes itself from open-web search and from ask_pipeworx, which is recommended for single lookups. The scope, return packet, and intended question type are all explicit.

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?

It gives explicit when-to-use guidance: broad/multi-part questions over structured data, and explicitly points to ask_pipeworx both for signed-out users and for single lookups. It also discloses the paid tier requirement for 'thorough' depth. This is model behavior for routing an agent to the correct alternative.

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