browser_click

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without mentioning side effects (e.g., potential navigation, waiting behavior), return format, or dependencies (e.g., requiring a prior snapshot). This is insufficient for a mutation tool.

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 concise, with a single sentence for the action and a brief list of args. It is front-loaded and efficient, though the args list is minimally formatted.

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 description lacks contextual completeness: it does not mention prerequisites (e.g., taking a snapshot first), potential outcomes (e.g., page changes), or error conditions. For a simple click tool, this is insufficient given the lack of annotations and output schema details.

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 coverage is 0%, but the description adds meaning: it explains ref as a reference like '@e5' or '@e12' and specifies session_id as 'Browser session ID'. This compensates for the schema gap, though session_id could be further clarified.

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 ('Click') and the target ('an element by its ref ID from the snapshot'). It distinguishes this tool from siblings like browser_navigate (URL-based) and browser_type (text input) by specifying the mechanism (ref ID).

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 implies usage for clicking elements identified by ref IDs from a snapshot, but lacks explicit guidance on when not to use it (e.g., for navigation use browser_navigate) or alternatives. It provides basic context without exclusions.

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