scraping_browser_snapshot

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

Annotations already declare readOnly, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context the annotations do not: that the snapshot yields refs for ref-based tools, and that filtered mode strips page text (with a security rationale in the schema). It stops short of describing size or stability of the snapshot, which keeps it at 4 rather than 5.

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?

Four short sentences, front-loaded with what the tool produces, then when to use it, then the fallback for text. No filler or restatement of the title.

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?

No output schema exists, and the description adequately characterizes the return value (ARIA tree of interactive elements plus refs) and its main limitation in filtered mode. Minor gaps such as snapshot size limits or behavior on pages that are still loading are not addressed.

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?

Only one optional parameter and schema coverage is 100%; the schema itself explains default false, token savings, and the sensitive-action rationale. The description adds one consequence ('A filtered snapshot does not include page text'), but otherwise defers to the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Capture an ARIA snapshot of the current page') plus exactly what the output contains: interactive elements with refs. This clearly separates it from siblings like scraping_browser_screenshot, scraping_browser_get_html, and scraping_browser_get_text, which are named or implied as different outputs.

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?

Gives an explicit precondition and an exclusion: 'Use this before interacting with elements to get proper refs instead of guessing selectors', and routes the agent to scraping_browser_get_text when page text is needed because a filtered snapshot omits it. The decision path is fully stated.

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