browser_click

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

The description discloses that the tool returns a fresh snapshot after clicking, which is important behavioral context. However, with no annotations, it lacks details on error handling, loading waits, or behavior for missing elements.

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 extremely concise with two short sentences. It is front-loaded with the action and resource, and every sentence adds value. No superfluous content.

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?

Given the tool has 4 parameters with no schema documentation and no annotations, the description is insufficient. It does not cover parameter details, error conditions, or usage context beyond the basic action. An output schema exists but its content is unknown.

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 0%, and the description adds no meaning to parameters. It does not explain the format of 'ref', the purpose of 'session_id', possible values for 'button', or the effect of 'double'. The description fails to compensate for the lack of schema documentation.

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 tool clicks an element by snapshot ref, including iframe elements. It is specific and unambiguous, but does not explicitly distinguish from sibling tools like browser_mouse_click or browser_hover.

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 provides no guidance on when to use this tool vs alternatives (e.g., browser_hover, browser_mouse_click). It does not mention prerequisites, such as obtaining a snapshot first, nor when not to use it.

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