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

The annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds substantial context beyond that: sign-in and paid-tier requirements, parallel facet decomposition, the findings packet with gaps[] and stable citations, the 'never invented' guarantee, a corrected field, and the last-hop-only limitation. A few of these details could be clearer, but the disclosure is strong.

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 information-dense, front-loading account requirements and the alternative tool before the core behavior. The later sentences about the corrected field and last hop are somewhat tangential, but they still add behavioral clarity and do not waste space.

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 explains the return packet, gap handling, citation URIs, and usage boundaries. The only omissions are latency and explicit error conditions, which are not essential for selecting and invoking 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?

Schema description coverage is 100%, so the baseline is 3. The description adds the actionable caveat that depth:'thorough' requires a paid plan and gives example question phrasings that clarify the natural-language question parameter, going beyond 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 opens with account requirements but quickly states the core: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources ... in ONE call' and explicitly contrasts this with 'NOT open-web search.' It also names ask_pipeworx as the single-lookup alternative, making the tool's purpose and scope unmistakable.

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 provides explicit routing instructions: use ask_pipeworx if not signed in or for a single lookup, and names search_within for single-source tasks via the corrected field. It also gives concrete examples of broad/multi-part questions that suit this tool, so an agent knows exactly when to select it.

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