browse_snapshot

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the output includes interactive elements and visible text, but it does not explain read-only behavior, login requirements, page-load assumptions, truncation, or how max_nodes limits results.

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 front-loaded sentence with no wasted words. It efficiently states the return content and element attributes.

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 annotations, no output schema, and 0% schema description coverage, the description should do more. It gives a high-level content summary but omits usage guidance, parameter semantics, truncation behavior, and the output format beyond a brief parenthetical.

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 only parameter, max_nodes, is completely undocumented in both the schema and the description. The description does not clarify whether it limits interactive elements, total DOM nodes, or text nodes, nor how the default of 220 affects the snapshot.

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 states a specific action and output: returning a compact snapshot containing interactive elements with selector/role/text plus visible text. This distinguishes it somewhat from pure text or screenshot tools, but it does not explicitly differentiate itself from siblings like browse_get_text or browse_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?

There is no guidance on when to use this tool versus browse_get_text, browse_screenshot, or other browsing siblings. It describes what is returned but gives no conditions, alternatives, or exclusions.

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