browser_snapshot

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

With no annotations, description carries full burden. Explains return format and purpose, but omits performance impact, size limits, or that snapshot is read-only. Lacks details on truncation behavior beyond what schema says.

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?

Two efficient sentences, front-loaded with action. No extraneous words. Every clause serves a purpose.

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?

Schema covers parameters well, but description doesn't explain what accessibility tree is, why use it, or how to choose parameters (compact vs interactive). Lacks guidance on interpretation. Adequate but not complete.

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?

All 5 parameters have detailed schema descriptions (100% coverage). Description adds no new parameter info; it only states output usage. Baseline 3 is appropriate as schema does the work.

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?

Clearly states 'Capture accessibility tree snapshot', verb+resource. Explains output (element references) and how they're used with other tools (click, type). Distinguishes from visual screenshot 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?

Implies usage as prerequisite for interaction tools, but no explicit when-not-to-use or comparison with siblings like browser_screenshot or browser_checkpoint. Lacks explicit guidance for complex vs simple tasks.

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