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

The description goes far beyond the readOnly/openWorld/idempotent annotations, disclosing account and paid-plan requirements, parallel routing across 5,798 tools, the findings packet structure, explicit gaps[] for unanswered facets, a no-hallucination guarantee, contradictions[] scanning, citation fetchability, semantic excerpting, and expected latency. This is rich, non-obvious behavioral context that annotations alone could not convey.

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 densely packed with operational detail, and it front-loads the most critical constraints (account required, who should use it instead). A few phrases are slightly redundant (the citation_uri explanation restates the earlier 'stable pipeworx:// citation'), but each major behavior earns its place for a tool with this much complexity.

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?

Despite having no output schema, the description fully specifies what the agent can expect: findings with evidence, confidence, source, fetched_at, citations, gaps[], contradictions[], and coarse timing. It also covers auth prerequisites, alternatives, and scope limits, so an agent has enough context to invoke the tool correctly and interpret its return packet.

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 on top by explaining that depth 'thorough' needs a paid plan, tying quick/standard/thorough to specific hop behavior, and clarifying that standard and thorough return contradictions[] while quick is single-hop. It supplements, rather than repeats, the schema's parameter documentation.

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 opens with a specific, differentiating statement: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources... in ONE call' and explicitly clarifies 'this is NOT open-web search.' It names the sibling tool ask_pipeworx as the alternative and positions deep_research as the right choice for broad/multi-part structured-data questions, making its purpose unambiguous.

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?

Usage is explicitly conditioned on account state: 'ACCOUNT REQUIRED... If you are not signed in, use ask_pipeworx instead.' It also states when the tool shines ('Best for broad/multi-part questions over structured data') and when not to use it ('For a single lookup use ask_pipeworx instead'), giving the agent clear routing logic.

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