click

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'click', without stating whether the action waits for navigation, scrolls elements into view, fails on missing targets, or has any side effects. For a tool that can trigger page changes, this is a significant gap.

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, terse Chinese sentence with no extraneous words. It front-loads the action and object. However, the brevity borders on under-specification, but for pure conciseness it earns a high score.

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 the tool's moderate complexity (nested target schema, multiple target kinds, double-click flag) and no annotations, this description is not complete enough. It does not explain the different target kinds (ref vs. locator path), when dblClick should be used, or what the output schema contains. The presence of an output schema reduces some burden, but the behavioral and usage gaps remain substantial.

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 description adds no meaning beyond the schema. It merely references 'target' while the schema already documents the target structure (ref, path, element selectors) and dblClick. With schema description coverage at 50%, the description should compensate for undocumented parameters, but it does not explain how to choose between ref and path or how dblClick alters behavior.

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 '点击指定 target 的页面元素' clearly states the action (click) and the resource (page element of the specified target). It distinguishes itself from siblings like input_text, navigate_to, and evaluate_script, which have different actions. However, it does not mention the double-click capability or any scope detail (e.g., current page), though the schema provides these.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, when clicking is appropriate (e.g., after a page snapshot), or when to prefer other tools like set_form_control or evaluate_script. The description leaves all usage decisions to the agent's inference.

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