playwright_click

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It adds one trait—degradation when Playwright is unavailable—but the degradation mechanism is undefined, and typical click behaviors such as waiting, visibility requirements, or navigation/JavaScript side effects are not mentioned.

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 two short sentences with the core operation front-loaded and a useful availability caveat second. It is slightly redundant with the tool name ('浏览器点击'), but it remains appropriately sized and scannable.

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 one-parameter click tool, the basic operation is present and the schema covers the selector. However, the degradation behavior is vague, and failure cases such as selector-not-found or element-not-actionable are not addressed, leaving meaningful gaps for an agent without annotations or an output schema.

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 input schema already describes the single parameter as a CSS selector, so schema coverage is 100% and the baseline is 3. The description merely restates that the click targets a CSS selector and adds no syntax, formatting, or fallback-specific parameter details.

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 states a specific action: clicking an element by CSS selector in the browser, which is clearly distinct from sibling playwright_navigate, playwright_screenshot, and playwright_assert operations. It does not explicitly name a sibling alternative, but the verb+resource pairing is enough to identify its role.

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 about when to use this tool versus the other playwright_* tools, and no exclusions or preconditions are given. The note about Playwright being unavailable is a behavioral fallback observation, not usage direction.

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