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

Adds substantial context beyond the read-only/idempotent annotations: explicit non-custody ('we never receive the funds'), the free tier ceiling of 10 calls/day, per-call pricing after that, and the two payment channels (x402 via params._meta or HTTP header, or X-API-Key credits). Rate limits and billing mechanics are exactly the kind of behavior an agent cannot infer from the schema.

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?

Front-loads the two capabilities before the cost/auth details, and every sentence carries information. The pricing/auth sentence is dense and slightly runs together, but it is not redundant filler.

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 zero-required-parameter generator with an output schema and full annotation coverage, the description supplies everything an agent needs to pick the mode, understand cost/auth, and reassure a human about custody. Return-value details are correctly left to the output schema.

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, but the description adds meaning the schema only hints at: that 'to' activates payment-link mode while 'text' is the plain encoding path, and that chain/token/amount belong to the payment variant. It does not spell out defaults or format constraints, leaving that to the schema.

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 two concrete operations with the resource named: an SVG QR code for arbitrary text/URL, or an EIP-681 payment link plus QR for a token amount to an address. It also frames the audience ('for an agent asking a human to pay'), which distinguishes it from verification/parsing siblings like payment_receipt_verify or http_link_parse.

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 a clear situational trigger ('when an agent asks a human to pay') and implicitly the mode split via the to/text fields. It does not name an alternative tool for the plain-encode case or state exclusions, so it stops short of full when-not guidance.

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