click_element

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

Discloses failure mode (isError with fix named), data staleness, and referential behavior for observe/settle_ms. With no annotations provided, the description fully bears the transparency burden and meets it well.

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 front-load the core purpose and essential guidelines. However, it could benefit from a brief parameter explanation, but overall efficient.

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 5 parameters, no output schema, and no annotations, the description covers usage context and failure behavior but lacks parameter details and full return semantics. Adequate but could be more complete.

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%, yet the description does not explain the individual parameters (button, instance, observe, settle_ms). Only id usage is implied, and others are merely referenced to click(). This is insufficient.

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 specific action (click), resource (element by id), and context (from parse_screen, no coordinate guessing). It effectively distinguishes from sibling 'click' which likely uses coordinates.

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 instructs to run parse_screen first, explains staleness of ids, and provides guidance on failure recovery (fix named). Also references click() for observe/settle_ms parameters.

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