render_html_screenshot

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

No annotations are provided, so the description carries the full burden. It discloses using Playwright chromium, waiting for images, hiding fixed/sticky elements, and supporting full-page or selector captures. However, it omits details like performance impact or side effects (e.g., file system writes).

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 a single, information-dense sentence that front-loads the core purpose. It is concise but could benefit from slight restructuring to improve readability (e.g., list key features).

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?

Given 13 parameters and no output schema or annotations, the description covers the main functionality and key options. It is fairly complete but could include notes on error handling or output format (PNG is implied) to fully inform the agent.

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 62%, and the description adds context for key behaviors (waiting for images, hiding fixed elements, full-page vs selector). For parameters like 'settleMs' and 'viewportWidth', the description does not provide additional meaning beyond the schema defaults.

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 creates a Playwright (chromium) screenshot of HTML content, specifying local/remote pages and element selectors. This distinguishes it from sibling tools like 'get_screenshot' and 'compare_html_to_image'.

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 details capabilities (image loading, hiding elements, full-page/selector captures) but does not explicitly state when to use this tool versus alternatives like 'get_screenshot'. No exclusions or prerequisites are mentioned.

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