Browser MCP Server

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

No annotations are provided, so the description carries full burden. It mentions the tool clicks an element but doesn't disclose behavioral traits such as whether it waits for the element to be clickable, handles errors if the selector is invalid, or what happens after the click (e.g., page navigation). This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's purpose and references documentation. It is front-loaded with essential information and contains no unnecessary words, making it highly concise and well-structured.

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 the complexity of a browser interaction tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like error handling, side effects, or return values, which are crucial for an AI agent to use the tool correctly in a browser automation context.

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%, with the parameter 'selector' fully documented in the schema as a Playwright selector. The description adds no additional meaning beyond this, such as examples or constraints, so it meets the baseline of 3 where 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 clearly states the action ('Click an element') and resource ('on the page'), specifying the mechanism ('using Playwright selector'). It distinguishes from sibling tools like browser_mouse_click by mentioning Playwright selectors, though it doesn't explicitly contrast with all alternatives like browser_press_key for keyboard interactions.

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 implies usage when clicking elements via Playwright selectors, with a reference to browser_docs for details, but doesn't explicitly state when to use this tool versus alternatives like browser_mouse_click or browser_press_key. It provides some context but lacks clear exclusions or comparative guidance.

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