browser_screenshot

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

The description discloses the return type (base64-encoded PNG), which is valuable. However, with no annotations, it carries the full burden and fails to mention preconditions (e.g., an active browser session) or behavioral details such as whether the screenshot captures the viewport or full page. It provides essential but not rich 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?

Two concise sentences with no wasted words. The description is front-loaded with the action and immediately provides the output format. Excellent conciseness.

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 simple parameterless tool with an output schema, the description covers the main purpose and return format. It lacks context about the browser session requirement and the distinction from the sibling 'screenshot' tool, but this is a minor gap given the tool's simplicity.

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?

The tool has zero parameters, so the input schema already fully covers this. The description adds no parameter information, which is appropriate. Baseline for 0 params is 4.

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') and the resource ('current page'), and specifies the output format. However, it does not distinguish this browser-specific tool from the sibling tool named 'screenshot', which could cause confusion about which tool to use.

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?

No guidance is provided on when to use this tool versus alternatives. With a nearly identical sibling named 'screenshot', the description should clarify the distinction (e.g., browser context vs. URL-based capture). This is a clear gap.

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