click

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

No annotations are provided, so the description carries full behavioral burden. It says nothing about whether the element is auto-scrolled into view, waits for actionability, how failures are reported, or whether the click targets a specific tab. For a core interaction tool this is a significant gap.

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?

A single sentence, front-loaded with the action and the accepted target formats, with zero filler. Nothing could be removed without losing information.

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 no annotations, no output schema, and one of two parameters undocumented, the description is too thin for a foundational click tool. It omits targeting scope (tabId), actionability/wait semantics, and failure behavior.

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 coverage is 50%: the target parameter is already documented in the schema with the same 'e12 or CSS selector' phrasing the description repeats, adding no new meaning, while tabId is undocumented in both the schema and the description. The description fails to compensate for the coverage gap.

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?

States a specific verb (click) and resource (an element), and explains how the target is identified via a ref from snapshot or a CSS selector, which implicitly links to the sibling snapshot tool. It does not explicitly differentiate from near-neighbors like dblclick or hover, but the verb itself is unambiguous.

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?

No guidance on when to use click versus alternatives such as dblclick, hover, press, or type, nor any conditions or prerequisites (e.g. element must exist first). The agent must infer usage entirely from the name.

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