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

Beyond the readOnlyHint, openWorldHint, idempotentHint, and non-destructive annotations, the description discloses output shape (findings packet with evidence, confidence, source, fetched_at, and stable citation), explicit gaps instead of invented answers, contradiction scanning for certain depths, semantic excerpting of large records, and expected latency. No statement 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 content is dense and genuinely useful, but the description is heavily repetitive: the multi-source explanation and the ask_pipeworx alternative are repeated multiple times in the provided text. This bloat reduces scannability and could be cut significantly without losing any information.

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: prerequisites, alternatives, input style, processing model, response packet fields, citation fetchability, gap handling, contradiction behavior, excerpting strategy, and timing are all covered. An agent has enough context to select and invoke the tool 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?

The schema already covers both parameters fully, including the depth enum and natural-language question guidance, so the baseline is 3. The description adds practical notes such as the paid requirement for thorough depth and latency expectations, but these are behavioral or access constraints rather than new parameter format or syntax semantics.

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 and resource: grounded multi-source research across Pipeworx's 1517 structured data sources in one call, with facet decomposition and parallel routing to 5,798 tools. It also explicitly says what it is not (open-web search) and contrasts itself with ask_pipeworx for single lookups, so an agent can distinguish it from the key sibling.

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 explicitly says when to use this tool: broad or multi-part questions over structured data, with concrete examples. It also gives exclusions: use ask_pipeworx when not signed in and use ask_pipeworx for a single lookup. This is clear when and when-not guidance with a named alternative.

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