browser_click

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

The description simply restates the tool's action without adding behavioral context beyond what annotations already provide (destructiveHint=true, openWorldHint=true). It does not disclose potential side effects like navigation, form submission, or state changes.

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, front-loaded sentence, which is concise. However, it is too brief and lacks sufficient detail to fully guide an agent, missing opportunities to add value without becoming verbose.

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, multiple siblings, no output schema), the description is severely incomplete. It omits return values, side effects, and usage context, leaving the agent underinformed for safe and correct invocation.

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 100% description coverage for all 5 parameters. The description adds no additional meaning beyond the schema, so the baseline of 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 states 'Perform click on a web page', which is a specific verb and resource. It distinguishes from sibling tools like browser_hover or browser_drag, though it does not mention parameter-driven variations like double-click or right-click.

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?

No guidance is provided on when to use this tool versus alternatives like browser_press_key or browser_hover. There is no mention of prerequisites, when not to use it, or how to choose between click and other interaction tools.

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