click

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

Annotations are absent, so the description must disclose behavior. It mentions 'visible element' as a constraint but fails to describe error handling (e.g., if element not found or multiple matches), safety implications (despite a 'confirm_dangerous' param), or what happens upon click.

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?

One sentence with no fluff. It front-loads the action and main locating methods. Could be improved by adding a second sentence on safety or parameter use, but remains efficient.

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 6 parameters, absence of annotations, and presence of an output schema, the description is insufficient. It lacks details on parameter interplay, error states, and behavioral guarantees (e.g., waits for element, scrolls into view).

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 0%, so the description must add meaning. It explains text, selector, and role but omits 'name', 'exact', and 'confirm_dangerous'. No guidance on exclusivity of locating parameters or the role of 'exact' for matching.

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 it clicks a visible element and lists three locating strategies (text, CSS selector, accessibility role). This distinguishes it from sibling tools like 'fill' (typing) and 'select' (choosing options), though it could explicitly differentiate from 'select'.

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 guidance on when to use this tool versus alternatives. Missing context on prerequisites (e.g., element must be visible, page must be loaded) and exclusions (e.g., not for hidden elements).

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