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. It mentions modes and click types that parallel the schema, but it does not disclose side effects, failure behavior, waiting semantics, or any other behavioral trait beyond what the structured fields already indicate.

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 front-loaded parenthetical with no filler, which is highly concise. It is slightly terse for a 13-parameter tool, but every phrase contributes directly to describing the tool.

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 13 parameters, no annotations, and no output schema, this description is incomplete. It enumerates capabilities but omits how the many parameters interact, when to prefer one targeting or mode option over another, and what behavior to expect during or after a click.

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 description coverage is 92%, so the schema already documents almost all parameters. The description groups and summarizes some parameter families (selector/text/coordinates, click types, modes), but adds no syntax, constraints, or format details beyond the schema.

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 names the specific action (click) and enumerates the supported targeting methods, click types, and modes. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools like mouse, mouse_down, or hover.

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 lists capabilities but gives no guidance on when to use this tool versus alternatives, nor how to choose between selector, text, or coordinate targeting. There is no when-to-use or when-not-to-use context.

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