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

Annotations already declare readOnly/openWorld/idempotent, and the description goes well beyond that: it discloses account and paid-tier requirements, parallel decomposition behavior, the findings-packet shape, explicit gaps[] for unanswered facets, the 'never invented' guarantee, contradictions[] in standard/thorough modes, semantic excerpting, and expected latency. There is no contradiction with 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 long and dense, but nearly every sentence carries distinct operational or behavioral value, and the critical auth/alternative information is front-loaded. It is not as tight or scannable as it could be, with no paragraph structure and some redundancy with the schema, but it is far from padded.

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?

For a complex tool with no output schma, the description is unusually complete: it explains the return packet, citation stability and fetchability, gap and contradiction semantics, excerpting behavior, latency, auth constraints, and alternatives. An agent has enough information to select and invoke the tool correctly in most cases.

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 description coverage is 100%, and the input schema already fully documents both params, including the depth enum and the paid nature of thorough. The description adds little new parameter-level meaning beyond latency expectations; the rest of the depth behavior is already in the schema, so it stays at baseline.

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 names a specific verb and resource: grounded multi-source research over Pipeworx's structured data sources, decomposed into facets and routed across 5,767 tools in parallel. It also explicitly contrasts itself with open-web search and with ask_pipeworx, making its scope and identity clear to an agent.

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 explicit when-to-use guidance (broad/multi-part questions over structured data), when-not-to-use guidance (single lookups should use ask_pipeworx), and an auth-based alternative ('If you are not signed in, use ask_pipeworx instead'). It also flags that depth:'thorough' requires a paid plan, which is directly actionable.

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