browser_take_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 that the tool takes a screenshot, can capture a single element or full page, but does not mention return format (e.g., base64) or potential side effects. Adequate but could be more detailed.

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 three sentences, each earning its place: first defines purpose, second gives usage guidance, third explains parameters. Front-loaded and no redundant text.

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?

The tool is simple with few parameters. The description covers purpose and parameter usage, but lacks explanation of the output (e.g., screenshot data format). Given no output schema, this is a minor gap.

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 explains how to use 'ref' for single element and 'full_page' for scrollable page, but does not mention 'session_id'. The description adds significant value for two key parameters.

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 explicitly states the tool takes a PNG screenshot for visual verification, distinguishing it from browser_snapshot which is for acting on elements. The verb 'take' and resource 'screenshot' are specific, and sibling differentiation is clear.

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 states when to use this tool vs browser_snapshot: 'To act on elements use browser_snapshot (not this); screenshots are for visually confirming what the page looks like.' It also explains parameters for single element or full page.

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