browser_snapshot

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

With no annotations, the description carries the burden of conveying safety and output behavior. It discloses that the output is an accessibility tree with element refs for AI interaction, which implies a read-only snapshot that supports later tool invocations. It does not explicitly state that the tool has no side effects, but the semantics of 'Get' and 'snapshot' strongly convey that.

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 directly communicates the core purpose and unique value. No filler words or redundant details are present.

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 adequately covers the tool's purpose and key output characteristics for an AI agent. Given the tool has no output schema, the description's mention of 'accessibility tree' and 'element refs' provides essential context, though it could elaborate on parameter effects like depth or compactness.

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 documents all five parameters with descriptions covering 100% of them, so the baseline is 3. The tool description adds no additional parameter semantics; it relies entirely on the schema.

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 uses a specific verb ('Get') and identifies a distinct resource ('accessibility tree snapshot with element refs'), clearly differentiating it from sibling tools like browser_screenshot or browser_get_html. It immediately conveys what the tool produces and why it exists (for AI interaction).

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 phrase 'for AI interaction' gives a clear context indicating this tool is meant to provide a page representation for AI reasoning and subsequent actions. However, it does not explicitly mention when not to use it or name alternatives, such as browser_get_html for raw DOM access.

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