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

Annotations already mark the tool readOnly/openWorld/idempotent/destructive=false, and the description adds substantial context beyond them: account and paid-tier requirements, expected latency ranges, the gaps[] behavior ('never invented'), contradictions[] on standard/thorough, citation_uri fetchability, and semantic excerpting of large records. Nothing contradicts 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 but front-loaded with the critical account requirement and maintains high information density throughout. Some content is redundant with the schema's depth descriptions and ask_pipeworx alternatives appear more than once, but given the tool's complexity and lack of an output schema, the length is mostly justified.

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 must explain return shape and it does: findings packet fields, gaps[], contradictions[], hop, citation_uri, and latency. It also covers auth, paid tier, use-case boundaries, and fallback alternative. An agent has essentially everything needed to decide and invoke 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% and the depth parameter already has a detailed enum description, so the baseline is 3. The description adds extra meaning: depth:'thorough' requires a paid plan, standard/thorough return contradictions[], and hop/citation_uri fields appear on findings. This goes beyond the schema, though some depth details are repeated rather than newly explained.

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 clearly states this is a 'grounded multi-source research' tool over Pipeworx's 1500 structured data sources and explicitly says it is NOT open-web search. It names the resource, the action, and distinguishes itself from the ask_pipeworx sibling family. This leaves no ambiguity about what the tool does.

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?

The description gives explicit when-to-use guidance: broad/multi-part questions over structured data are ideal, while single lookups and breaking/current-news topics should use ask_pipeworx. It also provides an exclusion condition ('If you are not signed in, use ask_pipeworx instead'). This is exemplary routing guidance.

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