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

Annotations signal read-only, open-world, idempotent, non-destructive behavior; the description adds substantial behavioral context on top: account/payment gate, structured-source limitation, explicit gaps[] for unanswered facets, resolvable citations, semantic excerpting, depth-dependent hops, timing estimates, and contradictions[] scanning. No contradiction with annotations exists.

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?

Long but information-dense; nearly every clause adds operational value (auth, scope, outputs, alternatives, timing, citation behavior). It is front-loaded with the account requirement and the ask_pipeworx fallback. The length is justified for a tool this complex, though it could be lightly restructured into clearer paragraphs.

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?

Despite having no output schema, the description specifies the findings-packet fields, gaps[], contradictions[], citation resolvability, excerpting behavior, latency, and depth semantics. An agent can select, invoke, and set user expectations for this tool without needing additional 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?

Input schema has 100% coverage of both parameters and detailed enum descriptions, so the baseline is 3. The description adds value beyond the schema by giving timing expectations per depth, clarifying the paid tier requirement, and reinforcing that broad/multi-part questions are the intended use — though it does not need to add format-level syntax.

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 structured data sources, with a clear mechanism (decompose into facets, route to tools in parallel) and outputs (findings packet). It explicitly distinguishes itself from open-web search and from ask_pipeworx, so an agent can tell siblings apart without opening their schemas.

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?

Gives explicit when-to-use guidance: best for broad/multi-part questions over structured data, use ask_pipeworx for single lookups and for unsigned-in users, and pair with ask_pipeworx for current events. This covers use, non-use, and the sibling alternative in clear terms.

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