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

With annotations already declaring readOnly/openWorld/idempotent=false, the description earns extra credit by disclosing JavaScript execution, output format and dimensions, fullPage's 4000 px cap, and the per-call pricing rationale that explains why repeats aren't free. It also states failed calls are free and that the tool changes nothing, matching the annotations.

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 behavior, then output shape, fullPage semantics, use cases, example, and pricing. Dense but nearly every clause is useful; payment details are slightly long but relevant given idempotent=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 explains the return payload (JPEG base64, final URL, HTTP status, title), sizing, and cost behavior. An agent has everything needed to call it correctly and interpret the result.

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 both parameters are documented there, including the 4000 px cap and 1280x800 viewport. The description adds only a sample URL value, so the schema largely carries this dimension — baseline 3.

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 — rendering a public page in headless Chrome and returning a JPEG screenshot — plus the returned metadata. This clearly differentiates it from metadata siblings like url_meta or url_favicon.

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?

Lists concrete use cases (visual checks, page previews, monitoring, feeding vision models) and an example call, which indicates when it's appropriate. It does not explicitly name alternatives or exclusions, so it stops 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.