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

With annotations present, the description goes well beyond them: it explains JS execution, the headless Chrome environment, the 4000 px height cap, pricing ($0.02/call via x402 USDC or card key, failed calls free), and even justifies the readOnlyHint=false annotation. That is unusually rich behavioral context for a mutation-flagged, open-world tool.

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?

The most decision-relevant facts (what it renders, what it returns) are front-loaded, and every subsequent sentence carries distinct payload: limits, use cases, example, pricing, and the read-only caveat. No filler or repetition of the tool name.

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 compensates by enumerating the return payload (screenshot, final URL, HTTP status, page title). Annotations cover the safety profile and the description adds cost, environment, and limits, leaving no material gap for an agent to invoke it correctly.

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 both parameters are already fully documented in the schema, and the description's fullPage note (4000 px vs 1280x800 viewport) largely restates it. The one addition is a concrete call example (url=..., fullPage=true), which only marginally exceeds the schema baseline.

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?

The description gives a specific verb+resource ('Render any public web page in a real headless Chrome browser') and specifies the exact artifact returned (JPEG, 1280 px wide, base64, plus final URL/status/title). It is clearly distinguishable from content-extraction siblings, though it never names the closest alternatives (extract_rendered, feed) explicitly.

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 states clear use cases ('visual checks, page previews, monitoring and feeding pages to vision models'), which tells an agent when this is the right pick over text-extraction siblings. It offers no explicit when-not or named alternative, so routing against extract_rendered is left to inference.

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