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

Despite readOnly/idempotent annotations covering safety, the description adds substantial behavioral context: account and paid-tier requirements, parallel routing across 5,798 tools, gaps[] for unanswered facets, contradictions[] for disagreeing findings, semantic excerpting, latency expectations, and the fetchability guarantee of citation URIs. 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 critical account requirement, but it is verbose and contains repetitive guidance about ask_pipeworx plus an awkward 'Then more:' transition that reads like an artifact. Not every sentence earns its place.

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 is unusually complete: it specifies the return packet fields, gap and contradiction behavior, excerpting strategy, latency, auth prerequisites, and sibling-tool routing. An agent has all necessary information to invoke it 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 schema already explains both `question` and `depth` in detail, so the baseline is 3. The description adds marginal peripheral context—example questions, latency implications of depth—but no new parameter-level semantics beyond what the schema provides.

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 states a specific verb+resource: grounded multi-source research across Pipeworx's 1517 structured data sources in one call. It also explicitly differentiates itself from open-web search and from ask_pipeworx, so an agent can distinguish it from siblings without guessing.

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?

Gives explicit when-to-use instructions: use ask_pipeworx if not signed in and for single lookups; use deep_research for broad/multi-part questions over structured data. It also explains depth tiers and when each is appropriate, 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.