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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so the bar is lower. The description adds meaningful behavioral context: JS, CSS, and web fonts execute in a real headless browser, and only public web pages are supported. No contradiction with 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?

Three sentences with no filler. The first sentence front-loads the primary action, the second clarifies output, and the third lists use cases. Every sentence earns its place.

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 six parameters, no output schema, and good annotations, the description covers purpose, behavior, and return type adequately. It could mention potential failure modes (e.g., private pages) but the 'public web page' qualifier implies this. Overall, it is complete for a screenshot 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 description coverage is 100%, so the schema already documents all six parameters. The description adds no extra parameter-specific meaning beyond reinforcing the url/html distinction and the format output, which is already covered. Baseline 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 clearly states the tool captures a screenshot image of a public web page or inline HTML snippet, with the specific verb 'Capture' and explicit resource. It distinguishes itself from sibling tools (extract_page, render_og, render_pdf) by mentioning real headless browser rendering and PNG/JPEG/WEBP output.

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 provides explicit use cases: visually preview a page, generate a thumbnail, or archive a point-in-time view. It does not mention when not to use or name alternatives, but the context is clear enough for an agent to select this tool for visual capture tasks.

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