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

Annotations already establish safe read-only, open-world, idempotent behavior, and the description adds rich non-contradictory context: decomposition into facets, parallel routing, findings-packet fields, explicit gaps rather than invented answers, citation_uri resolvability guarantees, contradiction scanning, semantic excerpting, and latency expectations. This goes well beyond the hint 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 information-dense and front-loaded with prerequisites and routing guidance. Almost every sentence earns its place, though a little tightening is possible since some depth semantics repeat the schema and 'use ask_pipeworx instead' appears twice.

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?

The description is unusually complete for a tool with no output schema: it covers prerequisites, scope, decomposition behavior, output packet fields, gap handling, citation fetchability, contradictions, excerpting, and time expectations. An agent has enough to decide when to call it and what to expect back.

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 carries the baseline burden; the description still adds value by giving example multi-part questions, clarifying that 'thorough' requires a paid plan, and stating latency expectations tied to depth. That is more than the input schema provides, even though much enum semantics are already present 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 specific verb and resource: grounded multi-source research across Pipeworx's structured data sources in one call. It explicitly contrasts with open-web search and with ask_pipeworx, so an agent can distinguish this tool from siblings without opening the schema.

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 conditions (broad/multi-part questions over structured data) and explicit alternatives: 'If you are not signed in, use ask_pipeworx instead' and 'For a single lookup use ask_pipeworx instead'. It also flags the paid-plan requirement for depth:'thorough', which is exactly the routing information an agent needs.

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