click_element

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

With no annotations provided, the description carries the full burden of disclosure. It clearly lists side effects (page navigation, form submission, DOM state change), prerequisites (visibility), and the return value (click coordinates). This is comprehensive and does not contradict any structured data.

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 three purposeful sentences, front-loaded with the main action and side effects, with no filler or repetition. Every sentence contributes value.

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 description covers purpose, side effects, prerequisites, alternatives, and return value. With no output schema, it explains what to expect (click coordinates). For a click tool, this is complete; nothing an agent needs to call it correctly is missing.

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 description does not add new meaning to the parameters themselves; the only extra context, the selector mutability constraint, is already present in 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 states a specific action ('triggers a native mouse click'), identifies the resource ('DOM element identified by CSS selector'), and notes the effects ('click handlers and form submissions'). It also distinguishes from siblings by naming alternatives 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?

It explicitly lists the intended use cases (buttons, links, checkboxes) and names the alternative tools for text input and complex interactions, giving clear routing. It also mentions the prerequisite that the 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.