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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds substantial behavioral context beyond them: auth requirements and paid-tier gating, latency expectations (15-60s, thorough up to ~90s), never-invents with explicit gaps[], a citation_uri resolvability contract, contradictions[] flagging for standard/thorough, and semantic excerpting of large records. No contradiction with annotations — the read-only framing is consistent throughout.

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?

Well front-loaded — auth, purpose, and the primary alternative appear in the first sentences — and every sentence adds facts. However, it is over-long with clear redundancy (ask_pipeworx routing stated twice, contradictions[] described twice, gaps[] repeated), and it contains a corrupted/garbled parenthetical fragment mid-description that an agent may misparse and that undermines confidence in the text.

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 carries the full burden of explaining return values and does so thoroughly: findings packet fields (verbatim evidence, confidence, source, fetched_at, citations), hop field, citation_uri fetchability, gaps[], contradictions[], auth tiers, data-source scope, and timing. The only meaningful gap is the garbled fragment that slightly compromises coherence for the agent reading it.

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 value by linking the depth enum to latency and cost (thorough requires a paid plan), explaining hop/gap-recovery behavior per depth level, and clarifying that the question parameter is meant for broad/multi-part input ('decomposition is the point').

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?

States a specific verb and resource — 'Grounded multi-source research across Pipeworx's 1506 STRUCTURED data sources... in ONE call' — with concrete example queries and an explicit description of the return packet. It distinguishes itself from siblings by asserting 'this is NOT open-web search' and by routing single lookups to ask_pipeworx, so an agent can separate it from the closest alternatives without opening their schemas.

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?

Explicitly states when to use it ('Best for broad/multi-part questions over structured data'), when not to ('For a single lookup use ask_pipeworx'), and an account-tier exclusion ('If you are not signed in, use ask_pipeworx instead — it works on every tier'). The named alternative and the conditions that select it are both given, leaving nothing to inference.

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