browser_click

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

The description adds no behavioral context beyond what the annotations already state; it doesn't note that clicking can trigger navigation, dialogs, or state changes. The destructiveHint and openWorldHint annotations are present, but the description itself contributes nothing new about side effects or requirements.

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 and is easy to scan, but it is under-specified: 'on a web page' is largely redundant for a browser tool and the sentence doesn't convey why or how the click is performed.

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 output schema, no usage guidance, and no behavioral notes, the description is too thin for an agent to fully understand invocation context. The parameter schema fills in target details, but important interaction semantics and when to choose this tool are missing.

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 the schema already documents target, button, modifiers, and doubleClick. The description adds no parameter-level meaning, so the baseline of 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?

The description says the tool performs a click on a web page, so the core action is clear, but it never mentions targets, snapshots, or click variants, making it generic. It also doesn't meaningfully distinguish this from the many sibling browser interaction tools beyond the name.

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?

There is no guidance on when to use browser_click versus browser_hover, browser_press_key, browser_drag, or browser_select_option. No context, exclusions, or alternative tool recommendations are provided.

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