browser_snapshot

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

There are no annotations, so the description must carry the full burden of disclosing behavioral traits. It states the snapshot is 'fast, text-based', implying a read-only, non-mutating operation, but it does not describe the output structure, whether it includes hidden elements, or any limitations. The description is too sparse to give the agent confidence about side effects or the exact nature of the returned data.

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, front-loaded with the core action, and contains no fluff. Every word adds value: 'accessible DOM snapshot' specifies what is retrieved, 'fast' indicates performance, and 'text-based' implies the format. It is appropriately terse for such a simple tool.

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?

With no parameters and no output schema, the description must convey enough for the agent to select the tool correctly among many similar siblings. It does not explain how this snapshot differs from 'get_accessibility_tree' or 'browser_extract_content', nor does it describe the output format beyond 'text-based'. This is insufficient for an agent to decide when to invoke it.

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 has zero parameters, so the schema is trivially complete. The description need not explain parameter meanings. The baseline for 0 parameters is 4, and the description does not introduce any ambiguity that would lower this.

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 retrieves an accessible DOM snapshot of the current page, using a specific verb ('Get') and resource ('accessible DOM snapshot'). It also adds a performance characteristic ('fast, text-based'). However, it does not explicitly distinguish this from the sibling 'get_accessibility_tree' or other snapshot-like tools.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when this is preferred over 'get_accessibility_tree', 'get_visual_map', or 'browser_extract_content'. Only a few adjectives ('fast, text-based') hint at a potential use case, but there is no explicit when/when-not.

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