scraping_browser_snapshot

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value by describing what the tool returns (interactive elements with accurate refs), which matters since there is no output schema. It omits any note on snapshot size or whether refs expire, but the core behavior is disclosed.

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?

Three short sentences, front-loaded with purpose followed by usage guidance. Minor redundancy between 'provides accurate element references' and 'get proper refs', but nothing wasteful enough to hurt comprehension.

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 and one optional parameter, the description adequately covers what comes back and how to use it. Safety is handled by annotations. A note on ref lifetime or re-snapshotting needs would make it fully complete, but nothing essential is missing for correct invocation.

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% and the single 'filtered' parameter is fully documented in the schema with its default and effect. The description says 'all interactive elements' but never mentions the compaction option, so it adds nothing beyond the schema. Baseline 3 is appropriate.

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 the distinguishing content ('all interactive elements with their refs'). This clearly separates it from siblings like get_html, get_text, and screenshot, which do not return refs.

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?

Explicitly tells the agent when to call it ('Use this before interacting with elements') and names the alternative it replaces ('instead of guessing selectors'). It doesn't name the specific downstream ref tools (click_ref, type_ref, wait_for_ref), but 'ref-based tools' is clear enough context.

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