click_role

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

With no annotations, the description carries the behavioral burden. It usefully discloses that multiple matches produce a candidate list rather than an arbitrary click. However, it does not describe behavior for unique matches, no matches, or what happens after a successful click, which are relevant for a mutating 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 two tight sentences with no filler. The main action and targeting mechanism come first, and the ambiguity guard is explained concisely by referencing click_text.

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 relatively simple and the schema covers all parameters, but there are no annotations and no output schema. The description covers the key ambiguity behavior yet omits edge-case behavior and post-click expectations, leaving the definition only partially complete for an agent with no other context.

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 100%, so the input schema already documents all four parameters. The description adds no extra meaning beyond confirming that role and name are the targeting criteria and that ambiguity is handled via the candidate-list 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 states a specific action ('Click element') with a clear targeting mechanism ('by ARIA role and name'). It also references the sibling click_text and signals how this tool differs, helping an agent select it over alternatives.

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 when to use this tool: when the element is identified by ARIA role and accessible name. It references click_text for the ambiguity guard but does not explicitly say when to prefer click_role over click_text or other click variants, nor does it state exclusions.

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