playwright__browser_click

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

The description is just a restatement of the tool's name and provides no additional behavioral traits. Annotations already flag destructiveHint=true and readOnlyHint=false, but the description does not add warnings about possible navigation, page changes, or the need for element permission via the 'element' parameter.

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 with no filler words. It is efficient but very minimal, which is why it does not reach the top score.

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 that this is a browser click that can trigger destructive or open-world side effects, the description is too bare to be contextually complete. It omits when to use it, what may follow, and how the element is specified from the page snapshot, despite the schema covering parameter formats.

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 parameter descriptions already document target, button, modifiers, doubleClick, and element. The tool description adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Perform click on a web page.' It clearly identifies the tool's action, though it does not explicitly distinguish it from sibling interaction tools like hover or press_key.

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?

No usage guidance is provided. The description does not say when to use this tool over alternatives such as playwright__browser_hover, playwright__browser_type, or playwright__browser_press_key, nor does it mention any prerequisites or exclusions.

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