web_click

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

The description discloses the primary behavior (clicks an element), but with no annotations, it lacks details on side effects (e.g., navigation, page changes), error handling, or required permissions. For a simple click action, the disclosure is minimally adequate.

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, concise sentence (10 words) that is front-loaded with the verb. Every word earns its place, with no wasted or redundant information.

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 simplicity (single required parameter, no output schema, straightforward action), the description is complete. It sufficiently enables an agent to understand when and how to invoke the tool.

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 coverage is 100% (ref parameter described), and the description adds a useful example ('@e3 from web_snapshot'). However, no additional semantic nuance beyond the schema is provided, meeting the baseline for high coverage.

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 clearly states the action ('Click'), the target ('an interactive element'), and the method ('by its ref, e.g., @e3 from web_snapshot'). It distinctly differentiates from sibling tools like web_scroll or web_type.

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?

The description implies use after obtaining a web_snapshot, but does not explicitly state when to use this tool over alternatives like web_navigate or web_scroll. No exclusion criteria or preconditions are mentioned.

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