browser_click

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

With no annotations, the description carries the full burden of disclosing side effects. It only states 'Perform click' without mentioning that clicks can trigger navigation, open new tabs, or require a stable page state. No behavioral traits beyond the literal action are disclosed.

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 short sentence, which is concise and free of fluff. However, it is under-specified to the point of being nearly a restatement of the tool name, so it does not fully earn its place by adding value.

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?

As part of a browser automation suite with no output schema and no annotations, the description should explain the tool's role in the workflow (e.g., that it follows a snapshot and uses the ref). It provides none of this context, making it incomplete for reliable agent use.

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 already provides detailed descriptions for both required parameters, covering 100% of them. The tool description adds no additional parameter meaning, so the schema properly handles semantic explanation; baseline 3 is appropriate.

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 identifies the action (perform click) and the target (web page), making the core purpose understandable. However, it does not differentiate from sibling interaction tools beyond the verb itself, and it is quite terse.

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 gives no guidance on when to use this tool versus alternatives such as browser_hover or browser_press_key. It also fails to mention the prerequisite of obtaining the element reference from a browser_snapshot, leaving the agent without critical context for correct invocation.

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