element_tap

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states 'click element' without mentioning potential side effects, authorization needs, or whether it requires the element to be in the current page. For a mutation action, this is inadequate.

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 short phrase with no wasted words, but it is under-specified. It lacks structure and any additional context that would help the agent, making it borderline between effective conciseness and insufficient detail.

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?

For a simple one-parameter tool, the description may be minimally sufficient, but given the abundance of sibling element tools, it does not clarify how element_tap differs from element_touch or element_trigger. It also omits details like required connection state or element visibility.

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%, and the description does not explain the element_id parameter. While the parameter name is self-explanatory, the tool description offers no additional context, such as how to obtain the ID or any constraints on it.

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 '点击元素' (click element) clearly states the action (click) and the resource (element). It is a specific verb-resource pair and is easy to understand. However, it does not differentiate from sibling tools like element_touch or element_trigger, which could be similar actions.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as whether the element must be visible or whether a connection is required, nor does it suggest when to prefer this over element_longpress or element_trigger.

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