click_element

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

No annotations are provided, so the description must carry the full burden. It discloses that clicking may change the page (new URL/title) and returns a screenshot. It mentions actionability checks and the force parameter. However, it does not describe error conditions (e.g., element not found, session invalid) or potential side effects.

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?

Two sentences: first states purpose and returns, second gives a specific usage hint for the force parameter. No unnecessary words; every sentence earns its place.

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 no output schema, the description adequately explains the return values (screenshot, new URL/title). It covers the key behavioral aspect of actionability checks via the force parameter. Missing some edge cases but sufficient for a straightforward click action.

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 100%, so the baseline is 3. The tool description repeats the schema's explanation for the 'force' parameter without adding new information. It does not clarify the 'selector' or 'session_id' parameters beyond the schema.

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 verb 'click' and resource 'element in a session page', and distinguishes from sibling tools like 'fill_form' or 'select_option' which perform different actions. The return value (screenshot and new URL/title) is also specified.

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 provides a specific when-to-use for the 'force' parameter ('use when overlays intercept pointer events'), but does not explicitly state when to prefer this tool over siblings like 'interact_and_test' or 'measure_interaction'. Usage is implied but not contrasted.

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