Playwright MCP Server

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

The description doesn't add behavioral context beyond what annotations provide. Annotations already indicate this is a destructive (destructiveHint: true), non-read-only (readOnlyHint: false), open-world (openWorldHint: true) operation. The description doesn't elaborate on what 'destructive' means in this context (e.g., might trigger page navigation or form submission), nor does it mention potential side effects, error conditions, or interaction requirements. However, it doesn't contradict annotations.

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 extremely concise at just four words, with zero wasted language. It's front-loaded with the core action ('Perform click') followed by the target ('on a web page'). Every word earns its place, making it easy to parse quickly.

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 destructive tool with 5 parameters and no output schema, the description is insufficient. It doesn't explain what happens after a click (e.g., page changes, navigation, JavaScript execution), doesn't mention dependencies on other tools like browser_snapshot, and provides no error handling context. Given the complexity and potential side effects of clicking in a browser, more guidance is needed despite good annotations.

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 parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond the basic action. It doesn't explain the relationship between 'element' and 'ref' parameters or provide examples of valid element descriptions. With complete schema coverage, the baseline score 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 'Perform click on a web page' clearly states the action (click) and target (web page), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like browser_hover or browser_press_key, which also interact with web page elements. The verb 'click' is precise but lacks context about what kind of click operation this is compared to alternatives.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose browser_click over browser_hover, browser_press_key, or browser_drag, nor does it specify prerequisites like needing a page snapshot from browser_snapshot first. There's no context about appropriate use cases or limitations.

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