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

Annotations already state readOnlyHint=true, openWorldHint=true, and idempotentHint=true, and the description adds substantial behavior beyond that: account/paywall requirements, parallel decomposition across 5,743 tools, gap[] behavior, hop fields, citations only when fetchable, contradictions[] for standard/thorough, semantic excerpting, and expected latency. 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 the tool is complex and nearly every sentence carries decision-relevant information such as auth requirements, alternative routing, return packet structure, depth semantics, and latency. It is front-loaded with the most critical constraint (account required) and the fastest alternative. It could be slightly more scannable with bullet structure, but it earns its length.

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?

There is no output schema, so the description carries the full burden of explaining return values. It does so thoroughly: findings packet contents, citation_uri behavior, gaps[], contradictions[], hop field, and latency. Combined with the auth guidance and depth explanation, an agent has enough to select and invoke the tool correctly without additional external context.

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, but the description adds meaningful depth semantics beyond the schema: it explains that standard adds a gap-recovery hop, thorough chases leads iteratively, and that depth affects both hops and contradictions scanning. This helps an agent choose the right depth value in context.

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 1500 structured data sources in one call. It explicitly distinguishes itself from open-web search and from the ask_pipeworx sibling, so an agent can tell what it is and what it is not.

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 when-to-use guidance: broad/multi-part questions over structured data. It also names ask_pipeworx as the alternative for single lookups and for unsigned-in users, and explains why deep_research would return empty gaps in those cases. This is concrete routing guidance, not just a general statement.

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