click

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

The description adds that the tool waits for visibility and enabled state, which is a behavioral trait beyond a simple click. However, it does not disclose failure behavior (e.g., timeout, error handling), click type, or scrolling. With no annotations, the description carries full burden but is incomplete.

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, straightforward sentence with no unnecessary words. It is front-loaded with the core action and condition.

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 has no output schema, no annotations, and a complex nested parameter. The description fails to explain the return value, error conditions, or the exact semantics of waiting. Given the large sibling set, more context is needed for an agent to use this tool effectively.

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 schema has 0% description coverage, meaning the parameters are not explained in the schema. The description does not add any meaning to the parameters; it does not explain the selector format or the timeoutMs meaning. The description fails to compensate for the low schema coverage.

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 ('Click') and the resource ('element') with a specific precondition ('after waiting for it to be visible and enabled'). This distinguishes it from siblings like 'retry_click' which retries, and 'interact' which is more general.

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 provides no explicit guidance on when to use this tool versus alternatives like 'retry_click' or 'interact'. Usage context is only implied by the description of the action, but no when-not-to or exclusion criteria are given.

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