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

Annotations already mark it read-only, idempotent, non-destructive, and open-world; the description builds on that with rich behavioral context: parallel decomposition across 5,743 tools, findings-packet shape, gaps[] never invented, contradictions[], always-fetchable citation_uri, hop fields, semantic excerpting, latency, and paid-tier requirements. No annotation is contradicted.

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?

Front-loaded with the account requirement and alternative before getting into internals, and packed with useful specifics. Long, but every sentence carries behavioral or routing information; minor repetition of ask_pipeworx and 'in one call' is a small cost given the complexity it covers.

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 describes the return packet: verbatim evidence, confidence, source, fetched_at, pipeworx:// citation, gaps[], hop, citation_uri, and contradictions[]. It also covers prerequisites, plan gating, latency, semantic excerpting, and fallback routing, so an agent has what it needs to call the tool correctly.

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% and already documents question and depth in detail, so the baseline is 3. The description adds operational meaning beyond the schema: thorough requires a paid plan, standard performs gap recovery, and questions may be broad/multi-part. It does not deeply expand on 'quick', but the schema already covers it.

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?

Description names a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1500 STRUCTURED data sources' decomposed into facets and routed in parallel. It explicitly contrasts with open-web search and distinguishes itself from siblings like ask_pipeworx, so an agent can tell them apart. The account and plan requirements are also stated up front.

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 ('Best for broad/multi-part questions over structured data') with example questions, and explicit when-not-to-use: single lookups and breaking/current-news should prefer ask_pipeworx. It also names ask_pipeworx as the fallback for unsigned-in users. This fully routes the agent to the correct alternative.

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