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

Goes well beyond annotations by disclosing the pricing/auth model ('$0.02 in USDC on Base per successful call, paid with x402'), that JavaScript is executed, the fixed 1280 px width, the 4000 px full-page cap, and the exact return payload. Open-world access is declared in annotations, but the cost and output-shape context here is genuinely additional.

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?

Four tight sentences, front-loaded with the core action and output, then the fullPage caveat, use cases, and cost. No filler and nothing buried.

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 carries the return-value burden and does so completely (JPEG, final URL, status, title). Payment requirements and capture limits are also covered, so an agent has everything needed for a correct call.

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 both parameters are already documented, including the 1280x800 default viewport. The description restates the width and fullPage height cap but adds no new syntax or constraint beyond the schema, so the baseline of 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?

States a specific verb and resource — 'Render any public web page in a real headless Chrome browser' — and specifies the exact artifact returned (base64 JPEG, final URL, HTTP status, page title). An agent can distinguish this from text-oriented siblings like extract or summarize without opening the 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?

Gives concrete usage contexts: 'visual checks, page previews, monitoring and feeding pages to vision models.' It lacks an explicit when-not or a named alternative (e.g. versus extract for text), so it stops short of full routing guidance, but the intended scenarios are unambiguous.

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