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

Annotations already declare readOnly/idempotent/openWorld, but the description adds genuinely new behavioral facts: a payment and on-chain settlement step precedes the fetch, an unquoted call yields a 402 with an auto-created quote, and a completed retry returns a prior receipt rather than re-executing. The notable omission is that a real monetary cost is implied without quantifying it or pointing at the pricing tool.

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 compact sentences, front-loaded with the purpose and precondition before the retry mechanics. Slight redundancy with the input-schema description, which repeats the 402-and-retry flow almost verbatim, but nothing is wasted.

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 tool with five accepted envelope shapes and a dozen URL aliases, the description does not orient the agent on which shape to send, and with no output schema it only hints at the return value ('receipt'). The critical commercial fact — that the call costs money and therefore needs a quote from a sibling tool first — is implied rather than stated.

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 the schema cannot express by naming the two required HTTP headers (Payment-Signature, X-XGuard-Quote) and tying 'quote' back to xguard.pricing.quote, but it says nothing about the accepted envelopes, the many deprecated URL aliases, max_bytes truncation, or method/mode choices.

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 ('Fetch one public HTTPS resource') plus the gating precondition (x402 v2 payment and on-chain settlement verification), which is far more than the title alone. It does not name the sibling tools (xguard.pricing.quote, xguard.preflight) that naturally precede it, so the agent must infer that a quote comes from elsewhere.

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 concrete invocation-flow guidance: call, receive 402, then retry the identical call with Payment-Signature and X-XGuard-Quote. That tells the agent how to proceed after failure, but there is no when-to-use vs. when-not guidance relative to the sibling quote/preflight tools, and no statement about what to do if settlement fails.

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