Bulk Screenshot Capture

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by describing the return format (JSON with per-URL results including download URL, status, error) and the limitation that multiple_scrolling is not supported. This is sufficient context beyond 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 four sentences, front-loaded with the primary purpose. It includes essential guidance and a note without extraneous information. It is concise, though the note could be integrated more smoothly.

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 the complexity (one array parameter with many fields), the description provides a reasonable overview: it explains the return format and key constraint. Without an output schema, it gives enough context for an agent to understand the tool's behavior. It could mention concurrency or error handling but is adequate.

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?

The input schema has 100% coverage, with detailed descriptions for each field. The description does not add additional meaning beyond the schema, so 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 screenshots of up to 50 webpages in a single request, specifying the action and scope. It distinguishes from sibling tools like screenshot_capture_scrolling by noting that scrolling video is not supported in bulk mode, and advises using web_fetch for CSS selector identification.

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 explicitly tells when to use this tool (for bulk screenshots) and when not (for scrolling captures, use screenshot_capture_scrolling). It also advises using web_fetch to obtain CSS selectors before calling this tool. This provides clear guidance on alternatives and prerequisites.

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