browser_click

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

No annotations are provided, so the description carries the full burden. It discloses the optional capture feature, but omits behavioral details such as side effects of clicking (e.g., navigation, state changes), timeout behavior, or element readiness requirements. This is under-transparent for an interactive action.

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 12-word sentence with no filler. It front-loads the core action and optional capture feature, 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?

With 5 parameters, no annotations, and no output schema, a one-sentence description is insufficient. It lacks clarity on timeout/wait behavior, session handling, return format, and when to use this tool versus siblings.

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?

Only 20% of parameters have schema descriptions. The description hints at captureChanges via 'optionally capture...' but does not explain the semantics of selector, timeout, waitAfterClick, or sessionId. With low schema coverage, the description fails to compensate.

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' with a clear resource ('an element') and mentions optional capture of DOM, console, network, and URL changes. This clearly distinguishes it from sibling tools like browser_fill or browser_press_key.

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 explicit when/when-not guidance or alternatives. However, the verb 'click' implies its use for clicking elements as opposed to filling or selecting, so usage is somewhat implied.

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