click

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds genuinely new behavior — consequential buttons (send, post, buy, delete, connect) are paused pending explicit user approval via `confirmed`, and browser confirm dialogs can be auto-accepted. That approval-gate semantics is the key non-obvious trait of this tool and is disclosed. Not fully transparent about what happens when confirmation is absent beyond being 'paused' (error? queue? no-op?).

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?

Front-loaded with purpose and targeting options, then the two behavioral caveats — a sensible ordering with no filler sentences. The line breaks and multi-line wrapping make it read as slightly fragmented, and the parenthetical "(e.g. "Messages")" example is doing more work than the surrounding prose.

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?

Covers targeting, the approval gate, and dialog handling for a mutation tool with no output schema — the essentials an agent needs to call it safely. Missing the stale-ref failure mode, session_id semantics, and ref-vs-text precedence, which matter for a stateful open-world browser 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 description coverage is 0%, so the description carries the load; it documents 4 of 5 parameters (ref, text, confirmed, accept_dialog) with examples and conditions. `session_id` is left undescribed and the precedence/conflict rule when both `ref` and `text` are supplied is unstated.

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?

States a specific verb ("Click") plus the two mutually exclusive targeting strategies (snapshot `ref` or visible `text`), with inline examples. An agent can immediately distinguish this from siblings like type_text, select_option, or press_key without opening any schema.

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?

Gives concrete operating context: `ref` must come from "the latest snapshot," which implicitly sequences snapshot → click, and it explains the text fallback's rationale ("keeps working when the page layout changes"). It also states exactly when `confirmed` must be true. It stops short of naming alternatives (e.g. use select_option instead of clicking a dropdown, or press_key for keyboard activation).

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