click

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

The description merely states 'click an element' without disclosing behavioral traits such as whether the cursor moves, if the app must be focused, or if there are side effects. Annotations (readOnlyHint=false, destructiveHint=false) are present but the description adds no additional context.

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 a single short sentence that conveys the core purpose without redundancy. It is front-loaded but could be slightly improved by separating the two methods (index vs coordinates) for clarity.

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 moderate complexity (6 parameters) and no output schema, the description lacks details about return values, error handling, or expected behavior after the click. It does not compensate for missing structured information.

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 coverage is 100% with descriptions for all six parameters. The description adds minimal extra meaning by framing the tool as clicking by 'index or pixel coordinates', which aligns with the schema. Baseline 3 is appropriate since schema already defines parameter semantics.

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 ('Click an element') and specifies two distinct methods ('by index or pixel coordinates from screenshot'). This differentiates it from sibling tools like drag, scroll, and type_text, which perform different operations.

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 implies usage for clicking based on screenshot coordinates or element index, but does not provide explicit guidance on when to use this tool versus alternatives like perform_secondary_action (right-click) or set_value (text input). No when-not-to-use or prerequisite information is given.

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