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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds substantial context beyond those: answers are 'never invented' with explicit gaps[], standard/thorough return contradictions[], citations are always fetchable via a resolvable pipeworx:// URI, large records are semantically excerpted rather than head-truncated, and latency expectations are disclosed (15-60s, thorough up to ~90s). No contradiction with 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 dense but well-organized, with critical account requirements front-loaded before the tool definition. Every sentence adds either usage rules, behavioral detail, or expected output. There is minor redundancy with the depth parameter already described in the schema, but given the tool's complexity, the length is justified and remains structured.

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?

With no output schema, the description fully specifies what the tool returns: findings packet elements (verbatim evidence, confidence, source, fetched_at, stable pipeworx:// citation), gaps[], contradictions[], the hop field, and citation_uri conditions. It also covers account requirements, pricing, latency, citation resolvability, and excerpting behavior—nothing an agent needs to invoke this tool correctly 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 question and depth thoroughly. The description adds value by disclosing that depth:'thorough' requires a paid plan, that 'standard' and 'thorough' include a contradictions[] scan, and by giving concrete latency expectations for depth choices. It also reinforces the question parameter's natural-language suitability with examples, slightly extending the schema's guidance.

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 names a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' that 'decomposes your question into focused facets' and 'returns a findings packet.' It explicitly distinguishes itself from open-web search and from the sibling ask_pipeworx by stating 'For a single lookup use ask_pipeworx instead,' so the agent can clearly tell it apart.

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 and when-not-to-use guidance: 'ACCOUNT REQUIRED... If you are not signed in, use ask_pipeworx instead — it works on every tier' and 'Best for broad/multi-part questions over structured data' with 'For a single lookup use ask_pipeworx instead.' It also notes that depth:'thorough' requires a paid plan, which is crucial for selection.

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