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

With no annotations, the description carries the full burden and does so well: it discloses JavaScript rendering, the exact output field image_base64, the $0.012 USDC cost on Base via x402, that billing occurs only on success, and how unpaid calls behave with retry via _meta["x402/payment"].

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 description is two compact sentences that front-load the capture result and then cover the payment behavior. Every clause earns its place by conveying output location, rendering behavior, cost, and failure/retry semantics.

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?

Despite having no output schema, the description identifies the return field image_base64 and explains the x402 payment success/failure flow. That is enough for an agent to call the tool and handle the paid-call protocol correctly.

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 single url parameter is already documented as a public http(s) page. The description adds context about JavaScript rendering and full-page scope but no additional syntax or constraints for the parameter itself, so baseline 3 applies.

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 description states a specific resource and output: the whole scrollable page captured as a base64 PNG in image_base64. The 'whole scrollable page' phrasing implicitly distinguishes it from the sibling screenshot tool, though it does not name that sibling explicitly.

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 clear context for when this tool is appropriate: full-page capture of a JavaScript-rendered page. It does not explicitly name the alternative viewport screenshot tool or provide exclusions, 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.