browser_click

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

Annotations declare readOnlyHint=false and destructiveHint=true, which already tell the agent this is a mutating and potentially destructive action. The description adds no behavioral context beyond a generic 'click' – it does not mention possible navigation, form submission, or other side effects that would be useful beyond the annotation flags.

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 single-sentence description is extremely concise but under-specified. It provides no structure or front-loading of key details like the required target parameter, and its brevity stems from omission rather than efficiency.

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?

For a tool with 5 parameters and no output schema, the description should explain how to specify the target (e.g., referencing the page snapshot) and what the click action accomplishes. The description is too skeletal to give an agent enough context to invoke it correctly, even though the schema covers parameter 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 description coverage is 100%, so all five parameters (button, target, element, modifiers, doubleClick) are fully documented in the schema. Per the rubric, a high coverage baseline of 3 applies. The description adds no parameter meaning beyond what the schema already provides.

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 'Perform click on a web page' states a verb and resource but is vague: it does not specify what is clicked (target element) or how it differs from sibling tools like browser_hover or browser_drop. It is close to a tautology of the name 'browser_click' with only a generic 'web page' context.

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 this tool versus alternatives such as browser_double_click (if it existed) or browser_hover. No mention of scenarios or exclusions, so an agent receives no help in selecting the right action.

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