browser_click

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

No annotations are provided, so the description bears the full behavioral burden and provides almost nothing: it does not say whether the click waits for the element, scrolls it into view, whether the tab must be focused or foregrounded, or what happens when no matching element exists. For a mutation-performing browser action this is a substantial gap.

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?

A single front-loaded sentence with no filler; the verb and target come first. It is efficient, though the enumeration of locator modes it does include is incomplete relative to the six-parameter schema.

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?

With no annotations, no output schema, and zero required parameters, the definition should clarify what happens when no locator is supplied and how the call reports success or failure. None of that is present, leaving the agent to guess at the most failure-prone aspects of a six-parameter click tool.

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 100%, so all six parameters are already documented, which sets the baseline at 3. The description adds a small amount beyond the schema by implying the three locator strategies (ref, selector, text) are interchangeable targeting options and by noting the tab may be active or specified, though it silently omits the x/y coordinate mode that the schema exposes.

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 and resource ('Clicks an element') plus scope ('on the active or specified tab'), which clearly separates it from siblings like browser_type, browser_select_option, and browser_scroll. No sibling is named as an alternative, but the action is unambiguous.

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 sentence lists which locator styles are accepted but gives no guidance on when to prefer one over another, no precedence rule when several are supplied, and no mention of when to use browser_type or browser_select_option instead. An agent must infer everything about selection strategy.

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