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

Beyond the readOnly/idempotent annotations, the description discloses account and paid-plan requirements, parallel decomposition across 5,798 tools, the return packet shape, explicit gaps[] with no invented answers, contradictions[] on deeper depths, resolvable pipeworx:// citation URIs, semantic excerpting, and latency expectations. There is no contradiction with 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 it earns its length for a complex tool: every sentence contributes useful context and the account constraint is front-loaded. A slight redundancy with the schema's depth explanations and the dense parenthetical style keeps it from a 5.

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?

This is a complex tool with no output schema, yet the description covers authentication, alternatives, depth semantics, output fields, citation resolvability, gap behavior, contradictions, and expected latency. An agent has almost everything needed to call it correctly and interpret the results.

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?

The input schema already describes both parameters completely, including the depth enum and what each level does, so this is at the baseline of 3. The description adds some operational context, such as example research questions and timing ranges, but it does not change or deepen the core meaning of the parameters.

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 opens with a specific verb+resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' in one call. It also explicitly distinguishes itself from open-web search and names ask_pipeworx as the sibling alternative, so an agent can tell it apart without opening the schema.

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?

The description gives explicit usage guidance: best for broad/multi-part questions over structured data, with concrete examples. It also gives clear exclusions: 'For a single lookup use ask_pipeworx instead' and 'If you are not signed in, use ask_pipeworx instead.' It further warns that this is NOT open-web search, preventing a common mis-selection.

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