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

Annotations already mark the tool read-only, idempotent, open-world, and non-destructive, so the bar is lower. The description adds substantial behavioral detail: parallel routing, findings packet contents, gaps[] for unanswered facets, never-invented claims, fetchable citation_uri conditions, contradictions[] for standard/thorough, semantic excerpting, and latency expectations. 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 unique content is front-loaded and genuinely informative, but the description is massively repetitive — near-identical blocks repeat multiple times, including account requirements, the grounded-research explanation, and the ask_pipeworx alternative. The excessive repetition undermines scannability and makes the description inappropriately large.

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 explaining return semantics, and it does: findings packet contents, verbatim evidence, confidence, source timestamps, stable citations, gaps[], contradictions[], and citation resolvability. It also covers auth, tiering, and latency. An agent has enough to invoke the tool and interpret results 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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by revealing that depth='thorough' requires a paid plan and by tying the question parameter to decomposition and broad/multi-part queries. It does not heavily expand parameter meaning beyond that, so 4 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?

States a specific verb and resource: grounded multi-source research across Pipeworx's 1517 structured data sources, with decomposition into facets and routing to 5,798 tools in parallel. It also explicitly distinguishes itself from siblings by naming ask_pipeworx as the alternative and clarifying this is not open-web search. An agent can clearly identify this as the broad structured-research tool.

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 explicit when-to-use and when-not-to-use guidance: use ask_pipeworx if not signed in, use ask_pipeworx for single lookups, and use deep_research for broad/multi-part questions over structured data. It also discloses account and paid-tier requirements for depth='thorough'. This is unusually explicit routing guidance.

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