browser_click

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partially covered. The description adds nothing beyond the action itself: it does not mention that the click may navigate, open dialogs, or submit data, nor the permission role of the 'element' parameter. Given a destructive, open-world tool, this is a thin description that leaves meaningful behavior undisclosed.

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?

It is a single, front-loaded sentence with zero waste, but it is undersized relative to a six-parameter destructive tool. Conciseness is achieved at the cost of all useful detail.

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?

No output schema exists, so the description should explain the post-click result (e.g., a new page snapshot). It also omits the session model, the permission flow implied by 'element', and the fact that clicking is open-world and potentially destructive. For a six-parameter, open-world interaction tool, this leaves major gaps.

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 all six parameters (button, target, element, session, modifiers, doubleClick) are documented in the schema with enums and defaults. The description adds no extra semantic context for any parameter, so the baseline 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?

States a specific verb ('click') and resource ('web page'), making the action unambiguous. However, it does not differentiate from siblings like browser_hover, browser_drag, or browser_type, and adds no scope detail (e.g., that the target must come from a snapshot).

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 when-to-use guidance, no exclusions, and no named alternatives. It does not say that the target reference must be obtained from browser_snapshot first, nor when to prefer browser_type or browser_fill_form over clicking.

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