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

Annotations already declare readOnly/openWorld/idempotent, and the description goes far beyond them: account/paywall requirements, 15-60s/~90s latency expectations, and detailed return semantics (verbatim evidence + confidence + source + fetched_at + pipeworx:// citation, gaps[] for unanswered facets, contradictions[] for disagreeing findings). It also discloses honesty guarantees ('never invented') and the condition under which citation_uri is present, which materially affects how an agent should consume results.

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 extremely dense but reads as a single run-on paragraph mixing auth, routing, mechanism, output format, hop semantics, and latency with no section breaks. Some depth mechanics ('standard' gap recovery, contradictions[]) duplicate what the schema's depth parameter already documents, and the editorial aside calling the tool 'Pipeworx's main workhorse' does not earn 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?

With no output schema, the description carries full responsibility for return-value disclosure, and it delivers: findings packet structure, hop field, gaps[], contradictions[], semantic excerpting, and the fetchable-citation guarantee. Auth, tiering, latency, and alternative routing are all covered. Minor omissions — error/rate-limit behavior and result-volume caps — keep this from a 5 for a tool this complex.

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 genuine value on top by tying depth levels to auth ('depth:"thorough" needs a paid plan'), latency bands, and hop behavior that the schema describes only abstractly. The question parameter is contextualized ('Broad/multi-part is fine — decomposition is the point'). No new syntax is introduced, but the pricing and latency constraints are real invocation factors 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 states a specific verb and resource — 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources' — and explicitly separates itself from open-web search ('this is NOT open-web search'). It names the closest sibling (ask_pipeworx) and gives concrete example questions, so an agent can unambiguously tell this tool apart from search_within, validate_claim, and the ask_pipeworx family.

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?

Routing guidance is explicit and front-loaded: 'If you are not signed in, use ask_pipeworx instead' and 'For a single lookup use ask_pipeworx instead.' It states the intended use case ('Best for broad/multi-part questions over structured data') and discloses the paid-tier requirement for depth:'thorough', letting an agent avoid a doomed or unauthorized call.

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