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

Beyond the readOnly/idempotent/non-destructive annotations, the description reveals important traits: it never invents answers and returns gaps[], includes contradictions[] for standard/thorough, only returns citations when they are fetchable, semantically excerpts large records, and states latency expectations of 15-90s. No statement contradicts 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 and every sentence adds operational or routing value, but it is a long single block that partly duplicates the schema's depth explanation. The account requirement is sensibly front-loaded, yet a little restructuring or trimming would improve scannability.

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 present, the description fully explains the return contract: findings packet with verbatim evidence, confidence, source, fetched_at, pipeworx:// citation, hop field, gaps[], contradictions[], and response-time expectations. It also covers access prerequisites and fallback tool routing, leaving no obvious gap for correct invocation.

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 coverage is 100% and the schema already explains both parameters in detail, including depth variants, defaults, and the paid nature of 'thorough'. The description adds an account prerequisite and example questions, but it largely restates the depth semantics already present in the schema, so its parameter-specific added value is modest.

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 1497 STRUCTURED data sources' that decomposes a question into facets and routes them to 5,724 tools. It also explicitly distinguishes itself with 'this is NOT open-web search' and contrasts with ask_pipeworx, so an agent can tell exactly what this tool does.

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?

Usage guidance is explicit and actionable: 'Best for broad/multi-part questions over structured data', 'For a single lookup use ask_pipeworx', 'For BREAKING or colloquial CURRENT-NEWS ... prefer ask_pipeworx', and 'If you are not signed in, use ask_pipeworx instead'. It also gives depth-selection guidance with the second-hop and paid-plan distinctions.

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