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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, and the description adds substantial context beyond those: account/paywall requirements, parallel facet decomposition, return packet contents, explicit gaps[] with never-invented behavior, contradictions[] behavior, citation_uri resolvability, semantic excerpting, and latency expectations. No contradiction with 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 long but information-dense, and nearly every sentence adds behavioral or routing value. Prerequisites are front-loaded, followed by purpose, output mechanics, depth variants, and latency. The main deduction is that some depth-variant details duplicate the input schema and the dense parenthetical structure makes it harder to skim.

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 tool with no output schema, the description thoroughly covers prerequisites, invocation context, output shape, evidence provenance, failure semantics, and performance expectations. It also explains when to switch to a sibling tool. Nothing an agent needs to select and call this tool correctly is missing.

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%, so the schema already documents the question and depth parameters. The description restates the depth behavior and adds a few contextual details like paid-plan gating and expected latency, but it does not materially expand parameter meaning beyond the schema's own descriptive enum values.

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: it performs grounded multi-source research across Pipeworx's structured data sources in one call, and explicitly distinguishes itself from open-web search. It also differentiates from sibling ask_pipeworx by noting it is not a single lookup, so an agent can tell them apart.

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: best for broad/multi-part questions over structured data, with concrete examples. It also gives when-not-to-use guidance: if not signed in, use ask_pipeworx instead; for a single lookup, use ask_pipeworx. This is clear routing with named alternatives.

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