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

The description does not disclose side effects, such as triggering navigation, form submission, or waiting behavior. It also fails to mention error handling or how the click is performed. The annotations only indicate that the tool is not read-only and interacts with an open world, which the description does not expand upon.

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, concise sentence that front-loads the core action. Every word contributes meaning, with no repetition or filler.

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?

The tool is simple, but the description still lacks critical context: it does not specify button options, double-click behavior, or the visible-text matching semantics in detail. The lack of usage guidelines and partial parameter coverage leaves the agent under-informed for reliable invocation.

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 0% schema description coverage, the description must compensate for lack of parameter documentation. It addresses 'selector' and 'text' but completely omits 'button' and 'double_click'. Parameters like 'button' default to 'left' but without further explanation, the agent may not know valid values or behavior.

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') and identifies the resource (an element) and matching mechanisms (CSS selector or visible text). It clearly communicates the tool's function and distinguishes it from sibling tools like type_text or fill_form.

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 is provided about when to use this tool versus alternatives, and no exclusions or prerequisites are mentioned. The description solely states what the tool does, leaving usage decisions entirely to the agent.

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