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. It only states the action but does not disclose behavioral traits such as success/failure behavior, waiting mechanics beyond the timeout parameter, or any side effects. Minimal transparency.

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?

Single sentence, front-loads the verb 'Clicks', and efficiently specifies the two locating methods without redundancy. Every part contributes meaning.

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?

No output schema, so return values are not described. The tool has 5 parameters, but the description covers the key aspects. However, for a click action, it may be adequate. Missing information on error states or preconditions.

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 high (80%), but the tool description adds value by explaining the relationship between selector and role/name parameters, clarifying that elements can be located either by CSS/text selector or by ARIA role with optional name. This goes beyond the schema's individual descriptions.

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 (Clicks) and the resource (an element) with two distinct locating methods (CSS/text selector or ARIA role with optional name). This unambiguously distinguishes it from sibling tools like fill, navigate, or screenshot.

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 explicit guidance on when to use click vs alternatives. While the sibling tools have different purposes, the description does not state when click is preferred or when not to use it. The distinction is implied but not articulated.

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