browser_screenshot

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

With no annotations, the description carries the full burden. It details execution timing behavior, timeout handling, and job_id for background tasks. However, it does not disclose the output format or side effects on the browser state. Partial transparency.

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, but the first sentence redundantly restates the name. The key execution timing guidance is front-loaded. Could be more concise by stating the purpose first and then timing details. Middle ground.

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 9 parameters, many browser siblings, and no output schema visibility, the description is incomplete. It ignores the main purpose and key parameters, failing to differentiate from similar browser tools. The timing advice is overly specific for a missing core.

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 0%, so the description must add meaning. It explains timing-related parameters (expected_runtime_seconds, timeout_seconds, etc.) but omits core parameters like session_id, name, selector, and full_page. These are critical for screenshot functionality and are left unexplained.

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 does not explicitly state what the tool does (e.g., 'capture a screenshot of the browser'). It assumes the purpose from the name, but the verb 'screenshot' is implied. The description primarily discusses execution timing parameters, not the core action.

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 usage guidance for timing parameters and on_timeout options, but does not indicate when to use this tool compared to sibling browser tools like browser_click or browser_html. No alternatives or context for selection are given.

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