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

Adds real behavioral context beyond annotations: budgetUsd 'is held while it runs and released' and 'Needs the write scope' — auth requirement and cost-hold mechanics the agent would not otherwise know. Annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) cover the safety surface, so this extras layer earns credit. No detail on failure/timeout behavior or media key expiry.

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?

Two tight sentences, front-loaded with the rendering behavior and capture modes, with cost/scope constraints following. Every clause carries information; no filler. Slightly dense, but no wasted sentences.

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?

For a screenshot tool with an output schema (so return format need not be explained), the description covers rendering model, capture options, cost mechanics, and the required write scope. Nothing essential to correct invocation 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 all five parameters are already documented in the schema. The description restates budgetUsd's default/max and viewport options without adding syntax or format info beyond the schema. Baseline 3 is correct 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?

Specific verb+resource: 'A real browser renders a URL ... returns the picture as a media key', with the three capture scopes (viewport, full page, one element) spelled out. It implicitly differentiates from text-oriented siblings like read_page by noting JavaScript runs and fonts load, but never names a sibling to route against. Clear purpose, no explicit sibling differentiation.

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?

Usage is implied by the JS-rendering framing (use when you need a real render rather than parsed text), but there is no explicit when-to-use/when-not or named alternative among the many page/render siblings (render_thumbnail, demo_page, inspect_page_style, capture_tweet). Adequate context, no routing guidance.

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