browser_click

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

无注解，描述承担全部行为披露责任。清楚说明了多元素匹配时返回提示而非超时，以及index参数的作用。但未提及点击是否触发页面导航等副作用，略有不足。

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?

两句话精炼概括核心功能，关键信息前置（点击和CSS选择器），无冗余内容。

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?

无输出模式，描述仅部分说明了返回（多元素时提示），未描述一般返回结构或错误处理。对于点击这种副作用操作，缺少等待页面等行为的说明，完整性一般。

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?

输入模式已100%覆盖两个参数的描述，描述未增加超过模式的新语义。baseline为3，描述虽提及index参数，但未提供模式外的额外信息。

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?

描述明确说明了工具的功能：在真实浏览器中点击CSS选择器指定的元素。动词'点击'和资源'元素'清晰，且提到了多元素处理。但未与兄弟工具（如browser_aria_click）进行区分，略失分。

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?

未提供何时使用此工具而非其他点击工具的指导。没有提及替代方案或排除条件，仅隐含适用于CSS选择器点击场景。

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