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

Even with annotations declaring readOnlyHint/openWorldHint/idempotentHint/destructiveHint, the description adds substantial behavioral detail: parallel decomposition across 5,798 tools, findings packet structure, verbatim evidence, gaps[] to avoid fabrication, contradictions[], semantic excerpting, latency expectations, and account/plan requirements. No contradictions 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 information-dense, and the most important operational guidance (account requirement and alternative tool) is front-loaded. Some redundancy exists (repeated emphasis on NOT open-web search and multiple mention of contradictions), but given the tool's complexity, the length is justified and each sentence contributes substantive guidance.

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 powerful tool with only two parameters and no output schema, the description covers everything an agent needs: authentication, alternatives, input semantics, internal behavior, output format, citation resolvability, failure handling via gaps[], and timing expectations. Nothing critical is missing for correct invocation.

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. The description adds meaningful context beyond the schema: it explains that depth:'thorough' requires a paid plan, that 'standard' and 'thorough' include gap recovery and contradictions[], and that the question can be broad/multi-part because decomposition is the point. This deepens the parameter semantics beyond the 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 clearly identifies a specific verb ('research') and resource ('1517 STRUCTURED data sources'), and explicitly contrasts itself with open-web search. It also distinguishes from the ask_pipeworx siblings by stating it is best for broad/multi-part questions over structured data, making sibling differentiation unambiguous.

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 provides explicit routing guidance: 'If you are not signed in, use ask_pipeworx instead' and 'For a single lookup use ask_pipeworx.' It also states depth-level prerequisites (thorough requires paid plan) and gives concrete example questions that fit the tool, so an agent knows exactly when to select it over alternatives.

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