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

Beyond the read-only, open-world, and idempotent hints, the description discloses account/paid-tier requirements, parallel routing across 5,798 tools, the findings packet shape, gaps[] semantics, fetchable citations, contradiction scans, semantic excerpting, and latency expectations. It adds substantial behavioral context without contradicting 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 dense but every sentence earns its place, and the access gate plus sibling alternative are front-loaded. Some sentences are long and parenthetical-heavy, but the overall order is logical: account requirement, core mechanism, output contract, depth behavior, performance.

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 compensates by specifying the return contract: verbatim evidence, confidence, source, fetched_at, pipeworx:// citations, gaps[], contradictions[], and excerpting behavior. It also covers auth, paid tiers, and latency, leaving an agent well-equipped to invoke and interpret results.

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 baseline is 3, but the description adds real value beyond the schema. It clarifies that the question can be broad/multi-part and that depth controls single-hop versus gap-recovery versus lead-chasing iterations, extending the enum descriptions 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?

The description states a concrete operation: grounded multi-source research across Pipeworx's 1517 structured data sources, with decomposition and parallel routing. It explicitly distinguishes itself from open-web search and from ask_pipeworx, so an agent can tell it apart 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?

It gives the account gate and says to use ask_pipeworx instead when signed out. It also defines the intended use ('broad/multi-part questions over structured data') and explicitly excludes single lookups, directing those to ask_pipeworx. Depth tiers are documented with their trade-offs.

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