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

Beyond the readOnlyHint/openWorldHint/idempotentHint annotations, the description discloses the findings packet fields, explicit gaps[] that are never invented, contradictions[] scans, the hop field, fetchable citation URIs, semantic excerpting, account/paid-plan requirements, and latency expectations. There is no contradiction with the 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 information-rich but structurally bloated. The ask_pipeworx distinction is restated at least four times, and the decision heuristic section repeats the same guidance in multiple forms. It would benefit from trimming redundant sentences.

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?

Despite having no output schema, the description covers inputs, auth prerequisites, paid depth tiers, scope, decomposition behavior, return packet contents, citations, gaps, contradictions, latency, and alternatives. An agent has everything needed to invoke it 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 description coverage is 100%, so the schema already documents the question and depth parameters. The description adds only marginal recursion on depth (paid plan, contradictions) and example queries, not substantial new parameter semantics beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: grounded multi-source research over Pipeworx's 1,506 structured data sources in one call, with facet decomposition and parallel tool routing. It also explicitly distinguishes itself from ask_pipeworx, so an agent can tell it apart from the sibling 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?

It gives explicit selection rules: use deep_research for broad/multi-part questions over structured data; use ask_pipeworx instead for single lookups or when not signed in; and it warns this is NOT open-web search. The routing guidance is direct and actionable.

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