browser_snapshot

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

Describes what each mode returns (YAML for aom, screenshot with overlays for hybrid) and implies read-only snapshot behavior. Lacks explicit statement about non-destructiveness or performance costs, but sufficient for a snapshot tool.

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 sentences, front-loaded with primary purpose, then details about modes. No redundant words; every sentence adds value.

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 output schema, description partially explains return values (aom and hybrid) but omits 'vision' mode return. Lacks complete coverage of all modes despite having only one parameter.

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 covers mode parameter with enum values and descriptions (100% coverage). Tool description adds useful context like 'token-lean' and 'Set-of-Mark screenshot', but 'vision' mode is only described in schema, not in main description.

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 'Take a snapshot of the current page' with specific verb and resource. Lists three distinct modes, differentiating from sibling tools like browser_scroll_read or browser_click which do other actions.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites or use cases relative to siblings like browser_scroll_read for reading text or browser_wait_for for waiting.

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