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

Goes well beyond the annotations: headless Chromium rendering, 25s timeout returning 504, 4000px fullPage clip, sub-request filtering, error billing exceptions, x402 USDC-on-Base pricing, and the untrusted-data warning. This is unusually complete behavioral disclosure for a read-only 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?

Front-loads what the tool does, then constraints, then behavior, then pricing. Dense but nearly every clause carries information; the terms URL and payment-rail detail are slightly tangential to invocation.

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?

With no output schema, the description helpfully enumerates return fields (imageBase64, mimeType, finalUrl, pageStatus, blockedRequests). The only completeness gap is the phantom delayMs parameter, which conflicts with the actual 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 schema already documents all five parameters including ranges and defaults. The description restates the ranges but also advertises a delayMs (0-3000) parameter that does not exist in the schema (additionalProperties: false), which could mislead an agent.

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?

Opens with a specific verb+resource: renders a public web page as PNG/JPEG. This is clearly distinguishable from siblings like fetch, pdf, and extract, which handle different content types.

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?

States the target must be a public http(s) URL and that private targets and sub-requests are blocked, giving clear preconditions. It stops short of explicitly naming when to prefer fetch or pdf instead.

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