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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses retention (30 days), size limit (≤ 5 MB), an allow-list of MIME types, a hard rejection rule (nothing executable), the return of a delete token, per-call pricing ($0.01 USDC via x402 on Base or Solana), and no-charge-on-bad-input behavior. These are exactly the operational facts an agent needs and are not derivable from the 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 purpose and URL result are front-loaded in the first clause, followed by limits, safety rule, and payment terms. It is dense but nearly every clause carries distinct, non-redundant information; the trailing pricing sentence is slightly overloaded but still earns its place.

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?

There is no output schema, and the description compensates by stating what the answer contains (the public URL and a delete token) and how payment/price negotiation works. For a write tool with a payment gate, this covers the full call lifecycle an agent must handle.

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 schema already documents all five parameters including the payment/encoding flow, and the baseline is 3. The description adds constraint context (5 MB cap, accepted formats, delete token in the response, no charge for bad input) but does not clarify per-parameter syntax beyond what the schema provides.

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 (upload) and resource (a file), plus the concrete outcome (a stable public URL of the form https://qrcode.pub/f/<id> lasting 30 days). This is clearly distinguishable from the sibling utilities page_metadata, page_to_markdown and qr_code without opening any schema.

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 makes the trigger condition clear (you need a fetchable public URL for a non-executable file) and explains the two-step payment flow: omit `payment` to get the price and payment requirements, or supply a signed PAYMENT-SIGNATURE. It does not explicitly say when NOT to use it or name an alternative for hosting, so it falls short of a 5.

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