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

With annotations already marking readOnly/openWorld/idempotent, the description adds substantial behavioral context: account/paid-tier requirements, parallel decomposition across 5,798 tools, findings packet shape, explicit gaps[] with a 'never invented' guarantee, contradictions[], and citation_uri only included when fetchable. No contradiction with the annotations exists.

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 front-loaded with the account requirement and alternative tool before explaining behavior. Every sentence adds distinct value, though the length is high and some details repeat the depth schema's descriptions.

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, so the description carries the full burden of explaining return behavior—and it does: findings packet fields, gap handling, contradiction reporting, citation resolvability, semantic excerpting, latency expectations, and auth constraints. An agent has enough context to invoke 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%, so the schema already documents both 'question' and 'depth' well. The description reinforces that broad/multi-part questions are fine and notes the paid requirement for 'thorough', but most of this is already in the schema, so the added parameter-level 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 concrete action ('Grounded multi-source research') on a specific resource ('Pipeworx's 1517 STRUCTURED data sources') and explicitly distinguishes itself from open-web search. It also differentiates from ask_pipeworx by targeting multi-part questions and noting when ask_pipeworx is the right alternative.

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?

The description gives explicit when-to-use and when-not-to-use guidance: 'If you are not signed in, use ask_pipeworx instead', 'For a single lookup use ask_pipeworx', and 'Best for broad/multi-part questions over structured data'. This routes an agent to the correct sibling without needing to infer.

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