browser_click

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Click an element' without mentioning error handling, waiting for element visibility, navigation side effects, or any other runtime behavior. This is a significant gap for a browser interaction action.

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 that states the action and parameters without superfluous words. It is succinct and easy to parse.

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 simplicity of the tool, the description covers the essential calling convention but omits important context such as return value, error behavior, or prerequisites. With no annotations and no output schema, the agent is left without information on what happens after the click or how failures are communicated.

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 schema provides no descriptions for the two parameters, but the description adds meaning by clarifying that 'selector' is a CSS selector and 'ref' is a reference from browser_snapshot. It implies these are alternative targeting methods, which is useful even though it doesn't explicitly state mutual exclusivity.

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 uses the specific verb 'Click' with the resource 'element' and clearly states the two identification methods (CSS selector or ref from browser_snapshot). This distinguishes it from sibling tools like browser_hover and browser_fill, making the tool's purpose immediately clear.

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 gives clear context that this tool is for clicking an element and mentions the input formats. It does not explicitly state when to avoid using it or provide alternative tool references, but the purpose is self-evident given the sibling actions.

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