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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses latency (15-60s, ~90s for thorough), the exact return packet (verbatim evidence, confidence, source, fetched_at, stable citations), gap handling with gaps[], contradictions[], the 'never invented' guarantee, and how citations remain fetchable. 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 long but front-loaded with the account requirement, purpose, and usage guidance before explaining output and latency details. It is well organized and nearly all content earns its place; minor redundancy in the repeated ask_pipeworx guidance and the tail detail prevents a 5.

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?

There is no output schema, but the description fully explains what the tool returns, including special fields like gaps[], contradictions[], and citations. It also covers prerequisites, paid-tier requirements, latency, and when to choose a sibling tool, so an agent has enough context to select and invoke it 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%, so the baseline is 3, but the description adds meaningful context beyond the schema: depth:'thorough' requires a paid plan, latency differs by depth, and the question parameter is illustrated with concrete research examples. This raises it above baseline without making the description the primary parameter reference.

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 specific verb and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' in one call, and explains that it decomposes the question into facets and routes them in parallel. It also distinguishes itself from open-web search and from ask_pipeworx, making its scope and role clear.

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 explicitly tells the agent when to use this tool — 'Best for broad/multi-part questions over structured data' — and when not to: 'For a single lookup use ask_pipeworx instead' and 'If you are not signed in, use ask_pipeworx instead.' This is strong, explicit routing guidance relative to a named sibling.

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