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

Annotations already mark this as readOnly, so the safety profile is covered. The description adds meaningful behavioral context beyond that: it captures the page as a real browser renders it after JavaScript execution, and it states the return format is a PNG image. This gives the agent important expectations about fidelity and output without contradicting 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?

The description is two sentences, front-loaded with the core action, then usage guidance, then return type. Every sentence earns its place and there is no redundant filler. It is concise without sacrificing the key differentiating information.

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?

The description, combined with the readOnly annotation and fully documented schema, gives an agent enough to select and invoke the tool correctly. It covers output type, rendering behavior, and common use cases. A small gap is the lack of constraints about external resource loading or timeouts, but these are not critical for the tool's primary purpose.

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?

All four parameters are fully documented in the input schema with descriptions, ranges, and defaults, so the schema carries the semantic load. The description itself adds no new parameter-specific meaning. Per the baseline for high schema coverage, a 3 is appropriate.

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 opens with a specific verb and resource: 'Take a screenshot of a web page' as it renders after JavaScript runs. This clearly differentiates it from reading HTML or extracting text, and the PNG return type distinguishes it from PDF-focused siblings. The purpose is immediately evident and not a tautology.

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 explicit use cases: checking a layout, confirming a site is up and looks right, or capturing what a user would actually see. It frames the tool as for 'seeing a page rather than reading it,' which provides clear context. It does not explicitly name when-not-to-use alternatives, but the guidance is strong enough to route an agent.

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