browser_snapshot

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It does not mention whether the tool is read-only, whether a page must be open, what happens on failure, or if it returns a structured snapshot. The phrase 'Get page structure' implies no side effects but does not confirm them.

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?

A single sentence with no redundant words. The verb and resource are front-loaded, and the parenthetical examples clarify the scope without adding bulk. It is maximally concise for the information it conveys.

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 is simple (no params) but has many siblings. The description lists a few element types but does not specify whether it returns a full snapshot object, whether it includes other elements, or how it differs from similar tools like browser_text or browser_observe. Since there is no output schema, the description is the sole guide and is only partially sufficient.

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?

The tool has zero parameters, so the description need not explain any parameter semantics. The schema is empty and trivially fully covered, so a baseline score of 4 is appropriate; the description adds no parameter-specific value but does not need to.

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 clearly states the verb 'Get' and the resource 'page structure', listing specific elements (title/url/button texts/inputs). This distinguishes it from siblings like browser_text (which likely extracts text content) and browser_elements (which may list all elements), though it could be more explicit about the output format.

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 is provided on when to use this tool versus the many browser_* siblings (e.g., browser_text, browser_elements, browser_observe). With such a large sibling set, the absence of any selection criteria leaves the agent to guess when a snapshot is appropriate.

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