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

Annotations already mark it read-only, idempotent, non-destructive, and open-world; the description goes beyond by disclosing account requirements, paid tier, latency expectations, gap reporting (never invented), fetchable citation_uri, contradictions[] for standard/thorough, and semantic excerpting. No contradiction with 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?

Information-dense but long and dense with nested parentheticals and redundant 'use ask_pipeworx instead' guidance. It front-loads the critical account requirement, but the one-paragraph structure makes it harder to parse than necessary.

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?

This is a complex research tool with no output schema, yet the description covers the return packet (evidence, confidence, source, fetched_at, citation_uri, gaps, contradictions), latency, access tiers, and behavior on large records. An agent has enough to invoke it correctly and interpret results.

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?

Input schema already covers 100% of parameters, including detailed enum explanations for depth, so the description isn't needed for basic parameter meaning. It does add behavior context (hop semantics, citation_uri) but these are more return-value details than parameter semantics; baseline 3 applies.

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 names a specific action (grounded multi-source research) and resource (Pipeworx's structured data sources), and states it is not open-web search. It distinguishes itself from ask_pipeworx, so an agent can tell it apart from siblings.

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?

Explicitly says to use ask_pipeworx instead when not signed in or for a single lookup, and says deep_research is for broad/multi-part questions over structured data. Also notes thorough depth requires a paid plan. This is direct when/when-not guidance.

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