click

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

The description discloses the return values (url, title, navigated, newPages), adding context beyond the annotation (destructiveHint=false). It does not contradict 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 concise with two sentences, no redundancy, and front-loads the core purpose. Every sentence adds value.

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 tool with 3 parameters and no output schema, the description covers purpose, usage, and return values adequately. However, it could mention that 'target' is required and the effect of 'returnSnapshot' more explicitly.

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 schema description coverage of only 33%, the description compensates by explaining the meaning of 'target' (element ref or CSS selector) and 'frameId' (for frames). This adds value beyond what the schema provides.

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') and the resource ('an element reference returned by snapshot or a CSS selector'). It distinguishes from sibling tools like hover, click_at, and drag by specifying the type of target.

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 usage guidance for frameId ('Use frameId with selectors inside a frame'), but does not explicitly differentiate when to use this tool versus alternatives like click_at or when not to use it.

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