click

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention that the tool likely waits for the element to be actionable, what happens on timeout, whether it scrolls into view, or any side effects. The description is bare and provides only the basic action.

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 sentence that directly states the tool's purpose. It is appropriately concise for a simple action, though it is slightly under-specified in conveying full behavior. No wasted words.

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?

Given the tool has 4 parameters (all documented) and no output schema, the description is minimal but sufficient for a simple click action. However, it does not convey important behavioral context like wait behavior or error handling, which an agent would need to know for robust use. It is adequate but not complete.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description itself adds no extra semantic meaning beyond 'selector' — it does not explain button, timeout, or clickCount. Since the schema already handles parameter docs, this is adequate but not enhanced.

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 tool's action ('Click') and the target ('an element matching the given selector'). It uses a specific verb and resource, and while it does not explicitly name siblings, the action of clicking is distinct from hovering, filling, or selecting.

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 implies usage: use this when you want to click an element. It provides no explicit guidance on when to prefer this over sibling tools like hover or select, and does not mention any exclusions or prerequisites. The context is straightforward but not explicitly differentiated.

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