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

Even with readOnly/openWorld/idempotent annotations, the description discloses how the call behaves internally: facet decomposition, parallel tool routing, return packet contents, gaps[] never invented, contradiction scans for deeper depths, semantic excerpting, latency expectations, and auth/paywall limits. This is far beyond what the annotations alone communicate.

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 information-dense and front-loaded with the most actionable constraints, but it is a long unbroken paragraph with a nonsensical final sentence and some repeated ask_pipeworx guidance. It would be stronger if trimmed and cleaned.

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?

There is no output schema, yet the description defines the findings packet fields, citation semantics, gaps[] behavior, contradictions, runtime ranges, and the account requirement. An agent has what it needs to decide whether this tool fits and what to expect when calling it.

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 description coverage is 100%, so the baseline is 3. The description adds the paid-plan restriction for the thorough depth and gives concrete question examples and latency implications not present in the schema, so it earns slightly more than the baseline.

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 operation: grounded multi-source research over Pipeworx's 1517 structured data sources, with facet decomposition, parallel routing, and a findings packet. It explicitly distinguishes itself from open-web search and from the ask_pipeworx sibling, making its purpose immediately identifiable. The stray 'Also note:...' tail is noise, but it does not obscure the stated purpose.

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?

It gives explicit routing guidance: signed-out users should use ask_pipeworx, 'thorough' requires a paid plan, and single lookups should use ask_pipeworx. It also states this tool is best for broad/multi-part structured-data questions, which tells the agent when to choose it over alternatives.

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