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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses detailed behavioral traits: parallel tool routing, findings with citations and confidence, explicit gaps[] rather than invented answers, contradiction detection, semantic excerpting, latency expectations, and hop behavior. 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 well front-loaded with the account requirement and core purpose. Every section earns its place, though some depth-related details overlap with the already-rich schema description, so a 4 is appropriate rather than a 5.

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 compensates by detailing the findings packet structure: verbatim evidence, confidence, source, fetched_at, stable citations, gaps[], contradictions[], hop field, and resolvable citation_uri. It also covers auth, latency, depth semantics, and alternatives, making the tool fully callable without external context.

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 most parameter documentation. The description adds value by explaining that depth:'thorough' requires a paid plan, describing latency implications per depth, and noting that standard/thorough return contradictions[]; this goes beyond the schema's enum descriptions.

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 1,517 structured data sources, decomposing questions and routing to 5,798 tools in parallel. It explicitly distinguishes itself from open-web search and from ask_pipeworx for single lookups, so an agent can tell it apart 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 gives explicit when-to-use guidance: best for broad/multi-part questions over structured data, while single lookups should use ask_pipeworx. It also states the account prerequisite and directs unsigned-in agents to ask_pipeworx instead, naming the alternative directly.

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