browser_click

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

The description transparently discloses the core actions (opening URL, clicking, returning the page) and provides an example. However, it fails to explain the behavior associated with the `max_links` parameter or any side effects, which is a gap given the lack of 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 highly concise, using two short sentences and a clear example. It is front-loaded with the action and leaves out any unnecessary detail, making it easy to parse.

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?

While the main functionality is well described, the presence of the `max_links` parameter and the existence of session-based sibling tools suggest additional context is needed for complete understanding. The description does not address these aspects, leaving some questions about edge cases and tool selection.

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?

The description adds crucial meaning to `selector` and `target_text`, and implies the role of `url` in the example, but it completely ignores `max_links`. Since the schema has 0% coverage (no parameter descriptions), the description only partially compensates for the missing information.

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 it opens a URL and clicks an element using either a CSS selector or link/button text, which precisely defines its purpose. This differentiates it from sibling tools like browser_navigate or session_click by focusing on the specific click action.

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 usage context is implied through the example and description, but there is no explicit guidance on when to use this tool over alternatives like session_click or browser_navigate. It lacks any mention of alternatives or exclusions, so it's only partially helpful for an agent deciding between tools.

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