click_element

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

No annotations provided, so the description fully covers behavioral traits: side effects (page navigation, form submission, DOM state modification), prerequisites, and return value. This compensates comprehensively for the lack of 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?

Two concise sentences: first states main action and side effects, second covers prerequisites, return, usage guidance, and alternatives. Front-loaded with key information, no unnecessary words.

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 one parameter with full schema coverage and no output schema, the description provides sufficient context: side effects, prerequisites, return, usage guidance, and alternatives. No gaps for an agent to effectively use this 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 covers the sole parameter 'selector' in detail (CSS selector, must resolve to single visible element). Description reinforces visibility requirement and adds context about operation failure if not met, adding some value beyond 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 tool's action ('triggers a native mouse click event') and resource ('DOM element identified by CSS selector'), and distinguishes it from siblings like 'fill_input' and 'evaluate_js'.

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?

Explicitly states when to use ('interact with buttons, links, checkboxes') and when not to use, with named alternatives ('fill_input' for text input, 'evaluate_js' for complex interactions). Also includes prerequisites (element must exist and be visible).

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