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

Beyond the annotations (openWorld=true, readOnly=false), the description discloses pricing per tier, that refusals are free and happen before payment, that a full SSRF fence applies, that caller cookies/headers are never accepted, and the exact payment handshake. This is exactly the kind of behavior an agent cannot infer from structured fields.

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?

It front-loads what the tool does and the output format, then stacks pricing, fence, preflight and payment mechanics. Dense and mostly earning its space, though the pricing is stated twice ('$0.03 per call' after the per-tier breakdown) and the run-on parentheticals make it slightly harder to scan.

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, yet the description says the return is a base64 PNG inline in JSON plus render metadata, and it covers the payment/authorization path an agent must traverse. Nothing needed to invoke it successfully is missing.

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% and the schema already documents url, tier, width and height, so the baseline is 3. The description adds meaning by tying tier selection to the price carried in the 402 challenge and by restating the body shape {url, tier?, width?, height?}, which clarifies which fields are optional in practice.

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?

The first clause names a specific verb and resource ('Screenshot of one public web page') and states the mechanism ('self-rendered by our own headless Chromium'), plus the input body shape and output form. An agent can distinguish this from render_bundle or access_crawl without opening a 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?

It gives concrete operational guidance: call without payment to receive the PaymentRequired challenge then retry with _meta["x402/payment"], and use the free preflight endpoint to validate shape and the SSRF fence before paying. It does not explicitly contrast with sibling render/bundle tools, which keeps it below 5.

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