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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely non-obvious behavior: this call returns a payment quote rather than data, and the actual read requires a separate HTTP GET plus x402 payment. Missing are quote lifetime/expiry and whether price varies with the query — material facts for an agent that must decide when to pay.

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 tight sentences, front-loaded with what is returned, then the critical 'does not return data' caveat, then the next step. Minor deduction for the terse leading fragment 'Stored change history', which reads as a label rather than a sentence and briefly obscures the subject.

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 no-output-schema quote tool, the description covers the return payload, the deliberate absence of data, and the two-step purchase path — enough for an agent to act correctly. It stops short of quote validity windows and the effect of `since` on pricing, which are the remaining gaps.

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 single optional `since` parameter is already documented as an ISO date, warranting the baseline 3. The description never mentions `since` and therefore adds nothing about whether it changes the quoted price or the quoted resource.

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 product ('Returns the x402 payment quote') and names the exact payload fields (price, network, asset, pay-to, URL), plus a negative clarification ('It does not return data') that prevents a costly mistake. The leading fragment 'Stored change history' only loosely identifies the resource being quoted, and the description never explicitly contrasts itself with the many other quote_* siblings.

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?

Gives the follow-up procedure concretely: GET the returned URL over HTTP and pay with x402, and check get_x402_health first — naming a sibling tool and the condition that selects it. It does not say when to prefer this over other quote_* tools or what to do if the caller already has an unexpired quote.

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