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

The description goes far beyond the annotations: it reveals auth requirements, parallel tool routing, output shape (findings packet with gaps[], contradictions[], hop, citation_uri), guarantee that citations are fetchable, semantic excerpting, and expected latency. This is consistent with readOnlyHint/idempotentHint/openWorldHint/destructiveHint=false; 'NOT open-web search' narrows the source type but still fits openWorldHint for external structured databases.

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 contains a large duplicated block: 'Grounded multi-source research... Best for... For a single lookup use ask_pipeworx instead' appears twice, and 'For a single lookup use ask_pipeworx instead' appears at least three times. It is one dense, poorly front-loaded paragraph, mixing core behavior with auth, examples, output details, and latency. Most individual facts are useful, but the redundancy and lack of structure earn only 2.

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 burden for return values and does so thoroughly: it enumerates verbatim evidence, confidence, source, fetched_at, citation_uri, hop, gaps[], and contradictions[]. It also covers auth, latency, depth-dependent behavior, and when to choose an alternative, so an agent can invoke 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 coverage is 100%, so the baseline is 3, and the description adds extra meaning: 'question' should be broad/multi-part and 'depth: thorough' requires a paid plan. It also reinforces the depth modes' behavioral differences already described in the schema. Only small additional parameter insight is present, so 4 rather than 5.

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 names a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources in ONE call,' and explains it decomposes questions into facets routed to 5,798 tools in parallel. It distinguishes itself from siblings by explicitly saying 'this is NOT open-web search' and pointing to ask_pipeworx for single lookups. The agent knows exactly what deep_research is for.

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, and directs single lookups to ask_pipeworx. It also handles auth tiers, saying unsigned-in users should use ask_pipeworx and that 'thorough' requires a paid plan. No ambiguity remains about selecting this tool versus the named alternative.

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