browser_screenshot

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

No annotations at all, so the description carries the full burden. It does disclose the key behavioral trait that the capture is of the background browser rather than the current foreground screen, but it says nothing about needing an open browser/tab, failure behavior, viewport vs full page, or whether the call perturbs page state.

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?

One sentence with no filler, and the core purpose plus the routing condition are front-loaded. The phrasing 'A picture of what the background browser shows' is slightly indirect compared to simply saying it captures the browser view.

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 zero-parameter, annotation-free tool with no output schema, the description covers what it produces and when to choose it. The remaining gap — prerequisites like an active browser session and capture scope — is modest but real.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No parameter semantics are needed or missing.

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 concrete verb+resource: a picture of what the background browser shows. It distinguishes itself from browser_read by targeting content that tool can't describe (images, maps, layouts), though it never distinguishes itself from the plain `screenshot` sibling.

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?

Gives an explicit selection condition: use this when browser_read can't describe the content — images, maps, or layouts. It lacks any when-not guidance or comparison against the sibling `screenshot` (full device) and `read_screen`, which an agent must otherwise infer.

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