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

The description discloses the auth requirement and paid tier, expected latency (15-60s, up to ~90s for thorough), parallel routing to 5,798 tools, explicit gaps[] with 'never invented', contradictions[] for standard/thorough, semantic excerpting, and resolvable citation_uri. Annotations (readOnly, openWorld, idempotent) are consistent — no contradiction — and the description adds substantial behavioral context well beyond 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 description is long but dense — nearly every sentence adds needed context (auth, scope, decomposition, output packet, depth differences, latency). Minor deductions because the purpose statement is deferred behind the account-requirement and fallback-tool sentences, and some depth behavior overlaps with the schema's enum descriptions.

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?

Without an output schema, the description thoroughly compensates by defining the findings packet: verbatim evidence, confidence, source, fetched_at, stable pipeworx:// citation, gaps[], contradictions[], hop field, and citation_uri resolvability. Combined with annotations and schema, an agent has enough to invoke the tool and interpret its result 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%, so the baseline is 3. The description adds extra semantics beyond the schema: depth:'thorough' requires a paid plan, latency implications for each depth, and the note that multi-step questions resolve in one call. It does not fully re-document parameters but enriches the practical meaning of depth.

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 names a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' in one call, with parallel decomposition into facets. It also distinguishes from siblings: 'this is NOT open-web search' and 'For a single lookup use ask_pipeworx instead.'

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.' It names an alternative and the switching condition: 'If you are not signed in, use ask_pipeworx instead' and 'For a single lookup use ask_pipeworx instead.'

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