click

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

No annotations are provided, so the description carries the full behavioral burden, and it is nearly silent: it does not say whether the click waits for navigation, scrolls the element into view, errors on a stale/detached ref, or what side effects a click may trigger. For an action tool with real side effects this is a substantial 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 short sentence with the key addressing mechanism front-loaded and no filler. It is efficient, though the brevity comes at the cost of substance rather than reflecting genuine completeness.

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 4-parameter action tool with no annotations and no output schema, the description omits the behaviours an agent most needs: wait/navigation semantics, failure modes on invalid refs, and the meaning of button and double. It is far too thin for the tool's complexity.

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 only 50%: ref and snapshot are described in the schema, but button (left/right/middle) and double are not documented anywhere. The description adds no meaning to any parameter, so it fails to compensate for the undocumented half.

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 gives a specific verb (click) and object (an element, addressed by its snapshot ref), so the action is unambiguous. It does not, however, distinguish itself from near-neighbours such as hover, press, or evaluate, so the agent gets no explicit routing cue beyond the verb.

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?

"By its snapshot ref" implies the prerequisite that a snapshot must exist first and that refs are the addressing mechanism, which is useful implied context. There is no explicit when-to-use/when-not guidance and no mention of when to prefer type, press, hover, or evaluate instead.

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