browser_snapshot

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

The description adds the context of 'accessibility snapshot', which goes beyond the readOnlyHint annotation by specifying the type of data captured. However, it does not disclose any behavioral traits like whether it returns a tree or formatted data, or any limitations on the snapshot depth or elements.

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 sentence that conveys purpose and a comparative advantage. It is front-loaded with the verb 'Capture'. However, it uses a comma splice and could be slightly more structured.

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 the tool has 4 parameters and no output schema, the description is insufficient. It does not describe what the snapshot output looks like (e.g., HTML tree, JSON), how to interpret the depth or boxes parameters, or when to use this over alternatives beyond a vague comparison.

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 input schema has 100% description coverage, so the schema already explains each parameter well. The description adds no additional information about the parameters, thus meeting the baseline but not exceeding it.

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 captures an accessibility snapshot of the current page, and distinguishes it from a screenshot by claiming it is better. However, it does not define what an accessibility snapshot entails, leaving some ambiguity.

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 only usage hint is 'better than screenshot', which implies a preference but does not specify when to use this tool versus other browser tools like browser_take_screenshot or browser_evaluate. No explicit when-not or alternative names are given.

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