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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds substantial behavioral context beyond that: account and paid-plan requirements, latency expectations, multi-hop gap recovery, contradictions scanning, never-invented gaps[], resolvable citation URIs, and semantic excerpting of large records. It does not contradict 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 but information-dense, and it front-loads the critical account-gating and routing information before the core functionality. Some redundancy exists with ask_pipeworx being mentioned twice, and the dense paragraph style could be improved with light structure, but every major sentence earns its place for a tool this complex.

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, the description carries the full burden of explaining return values, and it does: findings packet with verbatim evidence, confidence, source, fetched_at, citation_uri, gaps[], contradictions[], and hop fields. It also covers auth, paywall, latency, parameter semantics, and sibling routing. An agent has enough context to select, call, and interpret 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 description coverage is 100%, so the baseline is 3 even without additional parameter detail. The description reinforces depth behavior and adds paid-tier/latency context, but it does not materially change the meaning of the parameters beyond what the schema already documents. The question parameter's natural-language flexibility is also already stated 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 function: grounded multi-source research across Pipeworx's 1517 structured data sources, with decomposition into facets, parallel routing to tools, and a findings-packet return. It explicitly contrasts itself with open-web search and distinguishes itself from ask_pipeworx for single lookups. This is far beyond a restatement of the tool name and clearly differentiates it from siblings.

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 explicitly says this is best for broad/multi-part questions over structured data and gives concrete examples. It also states when not to use it: for a single lookup use ask_pipeworx instead, and if not signed in use ask_pipeworx since it works on every tier. This is explicit when/when-not/alternative guidance.

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