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

Annotations cover the safety profile (readOnly, idempotent, openWorld), and the description goes well beyond by disclosing the 6000px height cap, the fixed 1280px width, per-call pricing, and the concrete return payload fields.

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?

It is one dense sentence, but the descriptive core (what you get) is front-loaded and every clause carries distinct information (dimensions, cap, price, returns); the example JSON is slightly noisy but useful for the required url param.

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?

There is no output schema, so enumerating the returned fields (image_base64, mime, width, height, final_url, http_status, title, note) is exactly the compensation needed, and cost plus size limits are covered for a read-only 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 coverage is already 100%, so the baseline is 3, but the description adds real meaning to 'full_page' by stating the 6000px cap and contrasting viewport versus full page, information the schema does not contain.

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 ('See a web page') plus the concrete output format (1280-wide JPEG) and scope (any public URL, viewport or full page), which cleanly separates it from siblings like site_status and page_watch that also touch URLs.

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 description gives no explicit when-to-use guidance or alternative routing among the many URL/domain siblings (site_status, page_watch, bot_observatory). The 'any public URL' phrasing implies a context but doesn't state when a screenshot is the right call versus a status or monitoring tool.

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