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

Annotations already declare a safe read-only, idempotent, open-world profile, and the description adds substantial non-obvious behavior beyond them: account/paywall requirements, 15–90s latency expectations, the never-invented gaps[] guarantee, always-fetchable citation_uri, semantic excerpting rather than head-truncation, contradictions[] scans, and hop fields. This fully compensates for the absence of an output schema and contradicts nothing in 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 long (~330 words) but unusually dense — nearly every clause carries a distinct fact, and it is front-loaded with the most critical gate (account requirement) before the mechanics. It loses a point only for mild redundancy: the second-hop iteration paragraph partially restates the schema's depth description, and ask_pipeworx is routed to three separate times.

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 carries the full burden of return-shape disclosure and succeeds: findings packet fields, gaps[], contradictions[], hop, citation_uri resolvability guarantees, and edge-case behavior for out-of-catalog topics. For a complex 2-param tool with 30+ siblings and an auth tier requirement, nothing an agent needs to call it correctly is missing.

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%, setting the baseline at 3; the description earns one point above baseline by adding the paid-plan requirement for depth:"thorough" (absent from the schema) and clarifying that the question parameter is intentionally expected to be broad/multi-part. Most parameter meaning still lives in the schema's detailed depth enum description, so it does not reach 5.

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 states a specific operation — grounded multi-source research across 1,496 named structured data sources in one call — with concrete mechanics: decomposition into facets, parallel routing to 5,718 tools, and a defined findings-packet return shape. It explicitly negates open-web search and explicitly contrasts with ask_pipeworx, so an agent can disambiguate it from siblings without opening any other schema.

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?

Gives three explicit routing rules: use ask_pipeworx when not signed in, use ask_pipeworx for a single lookup, and prefer ask_pipeworx for breaking/current-news topics where deep_research returns mostly empty gaps[]. It states the positive condition — broad/multi-part questions over structured data — with two concrete example queries. Nothing is left to inference.

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