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

With no annotations, the description fully discloses key behaviors: deterministic (no LLM), SSRF-guarded, tamper-evident via Merkle proofs, cost $0.02/call, and authentication keyless x402 on Base mainnet. This exceeds typical transparency even with 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 efficient: a single sentence covering the core transformation, followed by concise bullet points on key features. Every sentence adds value (determinism, security, pricing) without redundancy.

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?

The description covers input constraints, behavior, and cost, but lacks explicit response structure details (e.g., JSON format). Given no output schema, this omission is notable but partially mitigated by mentioning 'receipt' and 'proofs'.

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 tool description adds high-level context (e.g., 'Merkle leaf') but does not significantly enhance understanding of individual parameters beyond what the schema already provides (format enum, urls format).

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 clearly states the tool's function: taking a list of URLs (≤20) and returning clean content for each plus a signed receipt with a Merkle root. This specific verb+resource combination distinguishes it from sibling tools like fetch or extract, which handle single URLs.

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 implies the usage context (batch processing of multiple URLs with verifiable integrity) but does not explicitly compare to alternatives. It is clear when to use (for 2-20 URLs requiring a receipt) but lacks guidance on when not to use, such as for single URLs or non-verifiable tasks.

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