browser_snapshot

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

The description does not mention any side effects or behavioral details, but the annotations (readOnlyHint: true, destructiveHint: false) already cover safety aspects. Since the description adds no extra behavioral context beyond the annotations, it meets the lower bar but does not exceed it.

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, concise sentence with no unnecessary words. It directly states the action and the primary benefit over a screenshot, achieving high clarity with minimal text.

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 description gives a basic understanding of the tool's function but lacks details about the return format or any limitations. Since there is no output schema, the agent is left without knowledge of what the snapshot contains or how it is structured, making it somewhat incomplete for fully informed usage.

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 schema already provides full descriptions for all four parameters (100% coverage), so the description does not need to elaborate. However, it also does not add any additional semantic value or examples, keeping it at the baseline for parameter clarity.

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's purpose with a specific verb ('Capture') and a specific resource ('accessibility snapshot of the current page'). It also adds a comparative note ('this is better than screenshot') that helps distinguish it from a related tool, making the intent unambiguous.

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 gives a vague comparative hint ('better than screenshot') but does not explicitly state when to use this tool over alternatives or provide conditions for its use. It lacks clear guidance on scenarios where an accessibility snapshot is preferred, making the usage guidelines only partially useful.

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