browser_click

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

The annotations already indicate that this is not read-only and is potentially destructive, so the description does not need to restate that. However, the description adds no additional behavioral context, such as whether clicks can trigger navigation, form submission, or page state changes beyond what the annotations already convey.

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 very concise and front-loaded, with no wasted words. It loses a point because it is so minimal that it provides little beyond the tool name and annotations.

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 five-parameter schema, no output schema, and many sibling browser tools, the description is too thin. It does not explain when to click, what side effects may occur, or how this differs from hover, press_key, or other interaction tools.

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%, so the input schema fully documents all five parameters. The description itself adds no extra meaning to the parameters, so the baseline of 3 applies.

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 action ('Perform click') and the resource ('web page'), so an agent knows what the tool does. It does not explicitly distinguish it from sibling tools like browser_hover or browser_press_key, but the basic purpose is unambiguous.

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 about when to use this tool versus alternatives, such as browser_hover, browser_type, or browser_press_key. The description does not mention any prerequisites, exclusions, or a preferred context for clicking.

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