js_click

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

No annotations provided, and the description lacks behavioral disclosures such as side effects, required permissions, whether it waits for events, or what happens on failure. It only states it's 'direct' and 'more reliable' without sufficient detail.

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 very concise (two sentences) and front-loaded with the key purpose. However, it could add a brief explanation of the parameter without becoming verbose.

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?

Despite having an output schema, the description fails to mention error handling, prerequisites, or whether the action is synchronous. The lack of annotation coverage and parameter clarity makes it incomplete for a tool with one critical parameter.

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 sole parameter 'ref' has no description in the schema (0% coverage) and the tool description does not clarify what it represents (e.g., CSS selector, element handle). The description adds no meaning beyond the schema's title.

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 performs a direct JS element.click() and distinguishes it from sibling 'click' by noting it's more reliable for React SPAs and Angular, especially when standard click fails due to event delegation.

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?

Explicitly says to use when click() does not trigger the handler, with an example (React 17+ delegation), providing clear when-to-use and implied when-not-to-use guidance.

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