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

Even with strong read-only/idempotent annotations, the description adds substantial behavioral context: findings packet structure, citation_uri fetchability, explicit gaps[], contradictions[], semantic excerpting of long records, latency expectations, and never-invented guarantees. No contradiction with annotations; the NOT-open-web-search statement is consistent with using 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 front-loaded with auth requirements and the sibling fallback, but it is long and structurally messy: the '(Second iteration: ...)' passage reads like an artifact and overlaps with schema content about depth. Every piece of information is useful, but the organization hurts readability.

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 explains the return packet's key fields, citation semantics, gaps, contradictions, latency, auth, and plan constraints. For a complex tool, this is enough for an agent to know when to call it and what to expect back.

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?

The input schema already has 100% parameter coverage, providing the baseline of 3. The description adds meaningful extras beyond the schema: thorough requires a paid plan, depth tiers map to additional passes, and expected latency varies by depth. It does not need to re-explain the question parameter since the schema already handles it.

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 names the verb and resource: it performs grounded multi-source research across Pipeworx's 1517 structured data sources in one call. It actively differentiates itself from siblings by saying it is NOT open-web search and by contrasting with ask_pipeworx for single lookups. The purpose is 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?

Usage guidance is unusually explicit: use ask_pipeworx if not signed in or for a single lookup, use deep_research for broad/multi-part questions over structured data, and thorough depth requires a paid plan. This gives an agent clear routing rules with named alternatives and conditions.

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