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

Beyond the annotations it discloses that JS is executed, the exact image dimensions and encoding, the fullPage height cap of 4000 px, the extra return fields, and — critically — the billing model: $0.01 per call, failed calls free, and repeats are not free. The cost and repeat-charge warning is exactly the kind of behavior an agent cannot get from readOnlyHint/openWorldHint.

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-loaded with the core render-and-return statement, then scoping, use cases, example, and pricing — every clause carries information. Minor redundancy in 'Reads or computes only and changes nothing', which largely restates readOnlyHint/destructiveHint=false.

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 fully carries the return burden: image format, width, base64 encoding, plus final URL, status and title. For a two-parameter tool with annotations already covering safety, cost disclosure and the fullPage caveat, nothing an agent needs to call it correctly 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%, so both parameters are already documented, including the 1280x800 default and 4000 px cap that the description restates. The only added value is the concrete example URL format, which is marginal; baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource — render a public page in headless Chrome with JavaScript executed and return a JPEG screenshot plus final URL, HTTP status and page title. That return payload also separates it from siblings like extract_rendered or url_meta, which an agent can distinguish without opening either 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 usage contexts (visual checks, page previews, monitoring, feeding vision models) and a worked example call. It stops short of naming an alternative tool or stating when not to use it, so the agent must infer that text-oriented siblings are preferable when pixels are unnecessary.

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