browser_screenshot

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It reveals basic behavior ('capture current viewport', 'private JPEG result') but omits important traits: whether it works on background/inactive tabs, permission requirements, error behavior if no tab is shared, impact on page state, or the actual dimensions captured.

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, focused sentence with no redundancy. It front-loads the action and key constraints. However, the brevity sacrifices necessary detail, making it efficient but not fully informative.

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 2 unannotated parameters, no output schema, and 33 siblings including multiple screenshot tools, the description is incomplete. It fails to clarify the return format (beyond 'private JPEG'), error handling, or differences from tools like browser_snapshot and browser_full_page_screenshot.

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% and the description does not mention either parameter ('quality' or 'collaboration_id'). The agent receives no explanation that collaboration_id identifies the shared tab or that quality controls JPEG compression, forcing reliance on parameter names alone.

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 action ('Capture'), the resource ('current viewport of one explicitly shared tab'), and the output format ('private JPEG result'). It distinguishes this tool from siblings like browser_full_page_screenshot and browser_region_screenshot by specifying 'viewport' and 'one explicitly shared tab'.

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 no guidance on when to use this tool versus alternatives (e.g., full_page_screenshot, region_screenshot, snapshot). It mentions 'explicitly shared tab' but does not explain prerequisites, limitations, or when not to use it.

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