playwright_click

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

There are no annotations to declare safe-read or destructive behavior, so the description carries the full burden. It only restates the action ('click') without disclosing that clicks may trigger navigation, require element visibility, or wait for page loads, which is risky for an unannotated mutation-like operation.

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. Every word adds value, and the parenthetical clarifies the parameter format without bloating the text.

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 one-parameter tool with an output schema, the description covers the essential action and selector type. However, it does not explain prerequisites or side effects, such as whether the interactive session must be active or that a click can cause navigation, making it adequate but not fully complete.

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?

With one required parameter and zero schema description coverage, the description compensates by specifying that the selector is a CSS selector, which is meaningfully more informative than the schema property title 'Selector'. It does not discuss selector matching details, but the format hint is sufficient for this simplicity.

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 a specific verb ('Click') and resource ('an element') plus the CSS selector format, making the tool's purpose immediately clear. The 'interactive session' qualifier differentiates it from sibling tools like playwright_navigate or playwright_fill.

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 phrase 'in the interactive session' provides clear context that this tool acts on elements within an established browser session. While it does not explicitly name alternatives like playwright_fill or playwright_text, the action of clicking is clear enough to imply when to use it.

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