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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint=true, and the description adds substantial behavioral context beyond that: account/auth requirements and paid-tier gating for 'thorough', parallel decomposition across 5,798 internal tools, gap[] never-invented policy, contradictions[] scanning, semantic excerpting rather than head-truncation, resolvable citation_uri guarantees, and timing expectations (15-90s). No contradiction with 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 tightly organized and front-loaded: the most critical operational constraint (account required + alternative) comes first, followed by purpose, mechanism, best-use, and depth details. Every sentence carries unique information for a complex tool with three depth modes, auth nuances, and a rich response contract; the minor redundancy with the schema's depth description prevents 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?

No output schema exists, but the description thoroughly covers the return contract: findings packet with verbatim evidence, confidence, source, fetched_at, citation_uri, hop field, gaps[], contradictions[], and large-record excerpting behavior. It also covers timing, auth, and depth differences — nothing an agent needs to invoke or interpret the result 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 baseline is 3. The description adds marginal value: it links the 'thorough' enum value to the paid plan, explains the hop/citation_uri mechanics behind depth levels, and ties the question parameter to the recommended use case ('Broad/multi-part is fine — decomposition is the point'). It mostly re-narrates the schema's already-detailed depth enum, so the increment is real but modest.

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 uses a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' — clearly stating what the tool does in one call. It also distinguishes itself from siblings by explicitly saying 'this is NOT open-web search' and naming ask_pipeworx as the alternative for signed-out users, so an agent can tell it apart without inspecting other tools.

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?

Gives explicit when-to-use guidance with concrete examples ('compare X and Y's regulatory + financial exposure'), explicit when-not-to-use ('For a single lookup use ask_pipeworx'), and a conditional routing rule ('If you are not signed in, use ask_pipeworx instead — it works on every tier'). This leaves no ambiguity about choice of tool.

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