browser_take_screenshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'take a screenshot' but does not state whether the screenshot is returned, saved to a file, or how the filename parameter affects behavior. It also does not mention side effects like file system writes or return format.

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 concise sentence that front-loads the action and includes the three key capture targets. Every word earns its place, and there is no fluff or repetition.

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 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on parameter usage, return values, file handling, and edge cases (e.g., what happens if both element and fullPage are set). The description is barely adequate for a simple screenshot, but not for the full parameter set.

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 compensate. It mentions 'full page' (likely mapping to fullPage) and 'referenced element' (element), but leaves ref, type, and filename unexplained. The relationship between ref and element is undefined, and the type parameter's enum is not described.

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 takes screenshots and specifies three modes: viewport, full page, and referenced element. This distinguishes it from other browser action tools like click or navigate, which serve different purposes.

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 purpose strongly implies when to use this tool (whenever a screenshot is needed), but there is no explicit mention of alternatives or situations to avoid. The sibling tool 'browser_snapshot' could be relevant, but the description does not clarify the difference.

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