点击元素

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

Discloses the behavioral detail of dispatching real mouse events (move, press, release) and guaranteeing hover/focus/event chains. It also mentions the overlays in the response. The readOnlyHint=false annotation already indicates mutation, and the description adds the mechanism without contradiction.

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 concise, with three sentences covering purpose, default behavior, and output overlays. No redundant information or filler.

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 description covers the core behavior and output (overlays). Given the output schema exists, it does not repeat all output fields, but mentions the important overlay aspect. It is sufficiently complete for an agent to use the tool correctly.

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?

All four parameters are described with 100% coverage. Each description explains the purpose clearly: element_id from find_element, by_js for obscured elements, observe for overlays, and use_action for choosing between Actions and simulated clicks. Default values are indicated.

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 tool's purpose as clicking an element, with a specific verb 'click' and resource 'element'. It distinguishes from sibling hover and other element operations by mentioning the default real mouse event dispatch, making the intent unambiguous.

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?

Provides usage guidance by explaining the default method (Actions) and the optional by_js for obscured elements. However, it does not explicitly contrast with hover or other click-like siblings, though the conditions for using by_js are given.

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