Playwright MCP

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by implying a click performs an action. However, the description adds minimal behavioral context beyond annotations—it doesn't specify that clicks can trigger navigation, form submissions, or JavaScript events, nor does it mention rate limits or authentication needs, leaving gaps in transparency.

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, direct sentence with zero wasted words—'Perform click on a web page' is front-loaded and efficiently conveys the core action. It earns its place by stating the essential purpose without unnecessary elaboration.

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 no output schema, the description is incomplete. It lacks details on return values (e.g., success/failure indicators), error handling, or dependencies like needing a prior browser_snapshot. Given the complexity of web interactions and sparse annotations, more context is needed for effective agent use.

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 100% schema description coverage, the input schema fully documents all 4 parameters. The description adds no additional meaning about parameters, such as explaining how 'element' and 'ref' work together or typical use cases for button types. This meets the baseline of 3 since the schema handles parameter documentation adequately.

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), distinguishing it from siblings like browser_hover or browser_type. However, it doesn't explicitly differentiate from browser_drag or browser_select_option, which also involve clicking interactions, so it lacks full sibling distinction.

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 like browser_drag (which might involve clicking) or browser_select_option (for dropdowns). It mentions no prerequisites, such as requiring a page snapshot from browser_snapshot first, leaving usage context implied at best.

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