playwright__browser_snapshot

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral detail that this produces an accessibility snapshot, not a screenshot, but it does not describe the output structure, pagination, or limitations. This is acceptable but not rich context.

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 the core action front-loaded. The '[playwright]' prefix is minor noise and the comparative claim adds some value, so overall it is efficient without being bloated.

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 tool has four optional parameters, full schema coverage, and annotations covering safety. The description gives enough to understand the core purpose and main alternative, but does not explain what an accessibility snapshot contains or how it relates to element references used by the 'target' parameter. It is minimally sufficient but has clear gaps.

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 description coverage is 100%, so the input schema fully documents all four parameters. The description adds no parameter-specific semantics, but the baseline of 3 is appropriate when the schema already carries that burden.

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 ('Capture') and resource ('accessibility snapshot of the current page'), making the action unambiguous. It also distinguishes itself from screenshot tools by claiming it is 'better than screenshot', which helps differentiate it from the sibling playwright__browser_take_screenshot.

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 clear context: use this tool to capture an accessibility snapshot rather than a visual screenshot. It names the general alternative ('screenshot') and gives a preference rationale, though it does not explicitly state when screenshots would still be preferable.

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