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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real substance: it will not fetch the URLs, spend USDC, or create an invoice, and it previews what the paid batch returns (provenance-linked snippets, hashes, titles, baseline comparisons). That is genuine behavioral context beyond the structured hints.

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?

Three sentences, front-loaded with the core promise, and each sentence carries a distinct fact (scope, paid-batch contents, protocol/usage). The x402 clause is dense but earns its place by preventing a wrong assumption about spending.

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 must cover returns; it specifies what the paid batch yields but only implies what the free quote itself returns (cost plus URL validation). For a 2-parameter read-only tool this is largely sufficient, with a minor gap on the exact quote response shape.

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 both urls and previous_hashes are already documented. The description reinforces the 10-URL cap and reframes previous_hashes as 'optional client-supplied baseline comparisons', which adds slight semantic value but does not exceed the schema's own detail.

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 (Quote) and resource (fixed cost for up to 10 public URLs) with explicit scope boundaries — no fetching, no USDC spend, no invoice. This cleanly separates it from the sibling quote_* tools that price other product categories.

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?

Clearly frames the usage flow: get the free quote, then use HTTP POST /v1/batch-web-intelligence after confirming the x402 payment challenge, and clarifies the quote is never a purchase. It stops short of naming which sibling quote tool to prefer for different workloads, so it lacks explicit alternatives.

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