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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), but the description adds genuinely new operational facts: the response is returned inline, capped at 1 MiB, the allowed MIME types, and that this tool bypasses credit accounting. That is meaningful disclosure beyond the structured fields, though error/failure behavior is not addressed.

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?

Purpose and output are front-loaded and the sentence count is low, but the trailing fragment "The screenshot" is a truncated, sentence-fragment artifact that adds no information and makes the definition look unfinished.

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 its weight by stating exactly what comes back (inline image file, PNG/JPEG/WEBP, ≤1 MiB), and the 9 parameters are well covered by the schema at 89%. Only the dangling final fragment and the absence of any failure/timeout behavior keep this from a 5.

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 89%, so the schema already documents url, width, height, quality, delay_ms, full_page, device_scale_factor and block_cookie_banners thoroughly. The description mirrors the notable knobs (viewport size, full page, retina scaling, cookie-banner hiding, format) but adds no format/syntax detail beyond what the schema provides, so baseline 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?

Specific verb and resource: "Capture a public web page as a PNG, JPEG or WEBP image" plus capability list (viewport size, full page, retina, cookie-banner hiding). The word "public web page" implicitly separates it from HTML-string siblings like html_to_image and html_to_pdf, but no sibling is named, so the differentiation is inferred rather than stated.

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?

The scope statement ("public web page", "Free tier only (credits do not apply to this tool)") implies when this tool is appropriate and flags that it is not credit-metered. However, it never says when to prefer this over close alternatives such as html_to_image, svg_to_png, or image_convert, and lists no exclusions beyond the public-URL restriction.

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