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

Despite having annotations, the description adds substantial behavioral context: account and paid-plan requirements, parallel decomposition, latency expectations, the findings packet structure, explicit gaps[] behavior, citation resolvability, hop fields, contradictions[], and semantic excerpting. It does not contradict the readOnlyHint, idempotentHint, or openWorldHint annotations; 'NOT open-web search' is consistent with using a closed catalog of grounded structured sources.

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 information-dense and front-loaded with the account requirement, but it is quite long and somewhat meandering, mixing usage guidance, return format, citations, and latency into one block. Every sentence carries value, but a complex tool like this could still benefit from tighter paragraph separation or trimming of repeated 'standard/thorough' details.

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?

For a two-parameter tool with no output schema, the description fully compensates: it covers prerequisites, alternative tools, expected latency, return structure, gaps behavior, citation semantics, contradictions, and depth differences. An agent has everything it needs to decide whether to call the tool and how to interpret the result.

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 both parameters are already documented in the schema. The description largely restates the depth semantics rather than adding new schema-independent meaning, though it does reinforce the account/paid-plan constraint around thorough. This meets the baseline but adds no significant parameter-level insight.

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 opens with a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1496 STRUCTURED data sources...' It clearly states this is NOT open-web search and contrasts itself with ask_pipeworx, making sibling differentiation explicit. The purpose is unmistakable and not merely a restatement of the title.

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' and 'For a single lookup use ask_pipeworx.' It also provides a concrete exclusion for breaking/current-news topics and notes that unsigned-in users should use ask_pipeworx instead. This leaves no ambiguity about tool selection.

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