browser_click

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Click an element' and to use the ref, but does not describe what happens on success, failure, whether the tool waits for element actionability, or any side effects. The description is too brief to inform the agent about the tool's runtime behavior.

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 two short sentences: 'Click an element. Use the exact ref from the latest snapshot.' It is front-loaded with the action and keeps every sentence useful. No unnecessary verbiage.

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 has no annotations and no output schema, so the description should explain return values and behavioral context, but it does not. It fails to mention what the tool returns (e.g., a snapshot, success status), how it handles missing or stale refs, or any permissions. Given the simplicity of the action, the description is too sparse to be fully complete.

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%, with detailed descriptions for both 'ref' and 'element'. The tool description adds only 'Use the exact ref from the latest snapshot,' which largely reiterates the schema's 'ref' description. Since the schema already documents the parameters thoroughly, the description provides minimal added meaning, warranting the 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 states the action clearly: 'Click an element.' This is a specific verb and resource. However, it does not explicitly differentiate from sibling tools like browser_right_click or browser_double_click, leaving some ambiguity about which click event is performed.

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 only guidance is 'Use the exact ref from the latest snapshot,' which explains how to reference the element but not when to use this tool versus alternatives. There is no mention of when to prefer click over hover, type, or other interaction tools, nor any exclusions or prerequisites beyond using the snapshot ref.

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