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

Even though annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, the description adds substantial behavioral context: parallel routing across 5,798 tools, explicit gaps[] for unanswered facets, a guarantee that findings are never invented, hop and contradiction passes for standard/thorough depths, semantic excerpting, and expected latency of 15-60s (up to ~90s for thorough). No contradiction with annotations was found.

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 front-loaded with the critical account requirement and fallback tool, and all major sections (data scope, output packet, depth behavior, latency, citation guarantees) serve the goal of correctly selecting and invoking a complex paid tool. It is dense but not bloated; each sentence contributes useful information.

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?

Because there is no output schema, the description carries the responsibility of explaining what the tool returns, and it does so thoroughly: verbatim evidence, confidence, source, fetched_at, stable pipeworx:// citations, gaps[], contradictions[], and hop fields. It also covers authentication, plan requirements, latency, and when to choose an alternative, so an agent has what it needs to call and interpret the tool.

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?

Despite 100% schema description coverage, the description materially enriches parameter understanding. It explains the practical meaning of depth (quick=3 single-hop, standard=3 default with gap-recovery and contradictions, thorough=6 paid with full iterative hop) and clarifies that question accepts broad/multi-part natural language. This goes well beyond the enum values in the schema.

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 describes the workflow (decompose question, route to tools in parallel) and the findings packet, so an agent can clearly identify what the tool does and how it differs from 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 usage conditions: account required, depth:'thorough' requires a paid plan, and directs unsigned-in users to ask_pipeworx instead. It also states when this tool is best ('broad/multi-part questions over structured data') and when not to use it ('For a single lookup use ask_pipeworx instead'), making alternative selection unambiguous.

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