browser_screenshot

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

No annotations are provided, so the description carries the full disclosure burden. It says nothing about what is returned (image bytes/encoding), whether the call is a safe read, or how the interaction with the active tab works. The only behavioral disclosure is the session_id default note.

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?

A single short sentence with no filler and the key constraint front-loaded. Slightly too terse for a four-parameter tool, but structurally sound.

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?

For a tool with four undocumented parameters, no annotations, and no output schema, the description is far too thin. It omits return-value behavior, the meaning of full_page/image_format/quality, and any precondition such as a running browser session.

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 all four parameters (quality, full_page, session_id, image_format) depend on the description. The description only addresses session_id; quality, full_page, and image_format remain entirely undocumented in both description and schema.

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?

States a verb+resource ('Capture the single agent browser') that, combined with the tool name, clearly identifies a screenshot operation on the single managed browser. It doesn't explicitly say it returns image data, so it falls short of the fully self-contained 5.

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?

'session_id is usually omitted' gives a genuine usage hint for that parameter, but there is no guidance on when to take a screenshot vs. the sibling browser_snapshot, browser_get_text, or browser_find_text, and no stated prerequisites (e.g., browser must be started).

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