Capture responsive screenshots

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

The annotations already carry destructiveHint=true and idempotentHint=true; the description adds useful nuance by saying existing matching files 'may be replaced' and noting the run occurs in a sandboxed local Chromium browser. This clarifies the mutation risk beyond the raw annotations, though it does not detail the output file naming pattern or external network behavior implied by openWorldHint.

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 sentences, no filler, and the core rendering-and-output behavior is front-loaded. The replacement caveat is placed at the end where it is easy to notice but does not obscure the primary purpose.

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 tool with full schema coverage, rich annotations, and an output schema, the description is largely complete: it covers input type, output type, destination, and destructive behavior. The only meaningful gap is the lack of explicit guidance on when to choose this tool over sibling tools, and the exact filename derivation for generated screenshots.

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 baseline is 3. The description loosely aligns targetPath with 'local HTML file or HTTP(S) URL' and outputDir with 'requested directory,' but it does not add new meaning beyond the schema, which already documents all three parameters and the viewport structure.

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 states a specific action ('Renders a local HTML file or HTTP(S) URL'), a concrete mechanism ('sandboxed local Chromium browser'), and a clear output ('writes PNG screenshots'). It distinguishes itself from sibling validation/metadata tools by focusing on visual capture rather than analysis or reporting.

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 intended use is implied: use this tool when a rendered screenshot of an HTML file or URL is needed. However, it does not explicitly state when to prefer this over sibling tools like html.local, html.url, or report.validation, nor does it mention any conditions or exclusions.

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