Click page element

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

Discloses key behaviors beyond annotations: LOCATOR_AMBIGUOUS for ambiguous locators, STALE_ELEMENT_REFERENCE for stale or cross-page refs, exact resolution requirements for iframe chains, and role locator name exactness. These error semantics and constraint details are valuable and not present in the annotations.

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?

Three sentences, each earning its place: main behavior, locator/iframe constraints, and durability advice. Highly front-loaded and free of filler.

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?

The tool has a complex locator schema and an output schema, so return values need not be described. The description covers the dominant complexities—locator types, iframe chains, exact matching, and error cases—but omits timeout semantics and the required session/page addressing parameters, leaving a small gap given the tool's complexity.

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 must compensate. It adds meaning for locator strategies, iframe chains, snapshot refs, and exact matching, but it does not explain sessionId, pageId, timeoutMs, or the ref pattern format beyond calling it 'short-lived.' This is partial but incomplete compensation.

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 specifies a precise action: 'Click exactly one semantic/CSS locator or short-lived snapshot ref on one explicitly addressed page.' It clearly differentiates from sibling tools like browser_double_click, browser_hover, and browser_focus by emphasizing exactly one click and explicit page addressing.

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?

Provides clear context on locator types, iframe constraints, and exact-match behavior. The final advice 'Prefer semantic locators for durable workflows' gives actionable guidance, though it does not explicitly name alternatives or state when not to use this tool versus siblings.

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