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

The annotations already declare read-only/open-world/idempotent behavior, and the description adds substantial context: auth requirements, paid depth tier, structured-only scope, output packet fields, gaps[] with a never-invented guarantee, contradiction[] behavior, citation fetchability caveats, excerpting behavior, and latency expectations. 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?

The description is dense and front-loaded with the account requirement and fallback tool, and nearly every clause carries an operational fact. However, 'It works on every tier' is repeated, and the single-paragraph structure makes an already long definition slightly harder to scan.

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?

For a complex tool with no output schema, the description covers prerequisites, alternatives, input suitability, output packet contents, citation limitations, gap handling, contradiction handling, excerpting, and expected latency. There is no critical information an agent needs that 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% and the enum descriptions are already rich, so the baseline is 3. The description adds extra parameter-relevant context such as example questions, account/paid prerequisites for depth, and the behavior shift between standard and thorough, though some of that repeats schema details.

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 operation and resource: grounded multi-source research across Pipeworx's 1517 structured data sources, with decomposition and parallel routing. It also explicitly distinguishes itself from open-web search and from ask_pipeworx, clarifying the single-lookup vs research boundary.

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?

Provides explicit when-to-use and when-not-to-use guidance: use ask_pipeworx if not signed in and for single lookups, and use deep_research for broad/multi-part structured-data questions with concrete examples. It also covers account tiers and depth selection, leaving little to inference.

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