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

Adds real context beyond the annotations: durable job queuing, the required polling step via render.job.get, and the billing rule that successful captures count against usage while failures do not. It does not mention auth requirements or rate limits, but the billing/async disclosure is substantive.

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?

Three tight sentences, front-loaded with the core action before the async and billing caveats. No filler; every clause carries information.

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?

An output schema exists so return values need not be described, and the polling pointer compensates for the async nature. However, with 13 parameters and low schema coverage, the description leaves several behavioral and parameter aspects undocumented for a fairly complex capture tool.

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 description coverage is only 46% across 13 parameters, so the description must compensate and largely does not. It alludes to the url/html oneOf by saying 'public web page or raw HTML', but adds no detail on the undocumented width, height, device, format, selector, or delivery semantics.

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: capturing a public web page or raw HTML as an image. It distinguishes itself from render.pdf.create and render.qr.create by naming the image output, though it does not clarify how it differs from the closely related render.clip.create sibling.

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 explains the asynchronous workflow (queued job, poll render.job.get) which is genuine usage guidance, but never states when to prefer this over render.clip.create, render.pdf.create, or render.template.render for overlapping tasks. Usage is implied rather than routed.

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