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

Even with readOnlyHint, openWorldHint, idempotentHint, and destructiveHint already set, the description adds substantial behavioral detail: parallel facet routing, findings packet content, stable resolvable citations, explicit gaps[] rather than invention, contradictions[] for deeper depths, semantic excerpting, and latency expectations. It does not contradict any annotation.

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 account requirement and organized by use case, behavior, output, and latency. It is dense and mostly non-redundant, though a bit verbose in places with repeated ask_pipeworx routing guidance and long enumerations.

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?

Given there is no output schema, the description fully covers expected return packet contents, citation behavior, gap handling, contradictions, latency, authentication, and pricing. An agent has everything needed to decide whether to call this tool and what to expect from the response.

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 depth levels, facet counts, the paid thorough tier, and that broad/multi-part questions are appropriate. The description adds examples and auth-related context, but those are more usage-level than parameter-semantic detail, so it does not meaningfully exceed the baseline set by the schema.

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 precise verb and resource: grounded multi-source research across Pipeworx's 1,540 structured data sources, decomposing questions into facets and routing to 5,908 tools in parallel. It also explicitly contrasts itself with open-web search and distinguishes itself from ask_pipeworx as the single-lookup alternative, making sibling differentiation clear.

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: best for broad/multi-part questions over structured data, with examples. It also states when not to use it: use ask_pipeworx for single lookups or when not signed in, and notes that thorough depth requires a paid plan.

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