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

Beyond the readOnly/idempotent annotations, the description reveals decomposition into parallel facet routing across 5,743 tools, output shape (verbatim evidence, confidence, source, fetched_at, citations, gaps[], contradictions[]), citation resolvability, semantic excerpting, latency, and paid-tier requirements. The claim that it is not open-web search is consistent with openWorldHint because it still draws on live external structured sources; no contradiction.

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: every sentence adds a distinct fact (auth, scope, routing behavior, output contract, alternatives, depth semantics, citation guarantee, latency). It is front-loaded with prerequisites and core behavior before descending into details, so the length is earned.

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?

With no output schema, the description must convey what the agent will receive, and it does: findings packet with fields, gaps[], contradictions[], hop, citation_uri, and latency expectations. It also covers auth/plan prerequisites and fallback tools, leaving no critical decision or expectation unresolved.

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 already documents question and depth fully (100% coverage), so the baseline is a 3; the description adds value by explaining that broad/multi-part questions are intended, that 'standard' recovers gaps while 'thorough' additionally chases leads and is paid, and by giving concrete example questions. This moves it to a 4.

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 concrete definition: grounded multi-source research across 1,500 structured Pipeworx sources in one call, and explicitly says 'this is NOT open-web search.' It also names the primary sibling (ask_pipeworx) and gives examples, making the tool's role unmistakable among the sibling list.

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 states exactly when to use this tool ('Best for broad/multi-part questions over structured data') and when not to: signed-out users and single lookups should use ask_pipeworx, and breaking/current-news topics are explicitly flagged as a poor fit. This is explicit exclusion plus named alternative.

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