browser_snapshot

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the comparative claim 'better than screenshot' but does not elaborate on behavioral traits like the snapshot's content structure, depth limits, or side effects. With annotations present, this is adequate but not exceptional.

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, short sentence that front-loads the core purpose. It is efficient and free of fluff, though it could benefit from slightly more detail without becoming verbose.

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?

The tool has no output schema, so the description should explain what an accessibility snapshot contains (e.g., element roles, names, states). It only gives a vague term. With four optional parameters and many sibling tools, the agent lacks guidance on what to expect from the output and how this tool fits into browser automation workflows.

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 coverage is 100%, and each parameter (boxes, depth, target, filename) has a clear description in the schema. The tool description does not add any additional meaning beyond what the schema already provides. Baseline 3 is appropriate as the schema carries the load.

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 tool captures an accessibility snapshot of the current page, using a specific verb ('Capture') and resource ('accessibility snapshot of the current page'). It also explicitly compares to the sibling tool `browser_take_screenshot`, distinguishing its purpose.

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 implies usage by claiming this is 'better than screenshot', providing context for choosing this tool over a visual screenshot. However, it does not explicitly specify when not to use it, nor does it mention alternatives beyond the screenshot comparison. Clear context but lacks exclusions.

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