browser_click

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

The description is a basic action statement and adds no behavioral context beyond what the annotations already convey (readOnlyHint=false, destructiveHint=true). It does not disclose potential side effects, permission requirements, or what happens after the click, so it offers minimal additional transparency.

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, concise sentence with no wordiness, which earns points for brevity. However, it is so minimal that it lacks useful structural elements like specifics on target or modifiers, making it only average in structure.

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's complexity (5 parameters, no output schema, many sibling tools), the description is severely incomplete. It omits any context about target references, permission flows, or behavioral effects, relying entirely on the schema and annotations. This is insufficient for an agent to use the tool confidently.

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 input schema provides full descriptions for all parameters (100% coverage), so the description does not need to explain them. The description itself adds little to parameter understanding, but the schema already carries the semantic load, resulting in a baseline score of 3.

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 ('a web page'), which is specific enough to understand the tool's basic purpose. However, it does not distinguish this tool from sibling tools like browser_hover or browser_press_key, so it lacks sibling differentiation.

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 alternatives, nor any mention of prerequisites such as obtaining a page snapshot or needing an exact target element reference. The description simply states the action without any context for appropriate usage.

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