browser_click

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

No annotations are provided, so the description carries the full burden. The description only states the action without disclosing behavioral traits such as whether the tool waits for the element to be actionable, whether it moves the mouse, what the default button is, or how it handles hidden elements. This is a significant transparency 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?

While the description is very short, it is under-specified rather than concise. It omits critical information about parameter usage and behavior, so it does not earn a higher score for efficiency.

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 complexity (4 parameters, no annotations, no output schema), the description is severely incomplete. It fails to explain return values, default behaviors, or usage context, making it nearly impossible for an agent to use the tool correctly based on the description alone.

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 no descriptions (0% coverage), and the description does not compensate by explaining any parameters. The four parameters (selector, button, timeout, clickCount) are not mentioned at all, leaving the agent to infer their meaning solely from names and enums.

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 primary action: clicking an element. It is a specific verb+resource pairing, but it does not differentiate from closely related sibling tools such as browser_mouse_click, browser_dblclick, or browser_tap, all of which involve clicking.

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. The description provides no context regarding prerequisites, typical scenarios, or distinctions from sibling tools like browser_mouse_click or browser_tap.

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