browser_click

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

With no annotations, the description carries the full burden. It discloses that right-click opens context menus, modifiers enable multi-select and open-in-new-tab, and double-click is supported. It does not describe error handling or return values, but it goes beyond the schema by explaining the effects of parameters.

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?

Two sentences, front-loaded with the core purpose, then capabilities. No wasted words.

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 lacks an output schema, so the description should mention what it returns, but it does not. It also omits error conditions or prerequisites beyond referencing the latest snapshot. For a simple click operation, it covers the main usage but misses return value and edge cases, so a 3 is appropriate.

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 schema already describes all four parameters, so the baseline is 3. The description adds value by explaining the effect of modifiers (multi-select, open-in-new-tab) and the right button (context menus), which is not in the schema. This elevates it above baseline.

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 verb (click), the resource (an element identified by its ref from the latest snapshot), and distinguishes itself from siblings like browser_hover and browser_drag by focusing on clicks. It also mentions supported button types and modifiers, clarifying its scope.

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 clearly indicates it is for clicking elements by ref from a snapshot, which is the primary click mechanism for DOM elements. It does not explicitly state when not to use it or name alternatives like browser_os_click, but the context implies it for ref-based clicks.

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