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

Annotations already say readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description goes beyond annotations by disclosing account requirements, paid depth tier, latency expectations (15-60s; ~90s for thorough), gap[]/contradictions[] behaviors, hop field, citation_uri fetchability, semantic excerpting rather than head-truncation, and parallel tool routing. This richly discloses behavioral traits beyond what annotations provide.

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; nearly every sentence adds behavioral or routing context. The usage guidance is front-loaded at the top, which is helpful. It is not maximally concise—some parentheticals could be tightened—but it earns most of its length with critical caveats and behavioral detail.

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?

Given this is a complex tool with no output schema, the description compensates fully: it documents return shape (findings packet elements: evidence, confidence, source, fetched_at, citation_uri, hop, gaps[], contradictions[]), latency, auth, alternatives, and depth tiers. An agent has enough to call it correctly and interpret results.

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. The description adds meaningful semantics: it explains what depth levels actually do (facet counts, hop behavior, contradictions[]), exceeding the schema's enum descriptions. It frames 'question' as naturally broad/multi-part, aligning with the decomposition behavior. Slight gap: no explicit mention that question is the only required param, but the schema already conveys that. Strong added value over 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+resource: 'Grounded multi-source research across Pipeworx's 1496 STRUCTURED data sources... in ONE call'. It clearly distinguishes from open-web search and mentions sibling ask_pipeworx explicitly, so an agent can differentiate. The scope and output type are clearly listed.

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?

Explicit when-to-use: 'Best for broad/multi-part questions over structured data'. It also gives a when-not-to-use: 'For a single lookup use ask_pipeworx instead' and 'If you are not signed in, use ask_pipeworx instead'. It names alternatives and conditions directly. This is exemplary routing guidance.

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