click_element

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

No annotations provided; description only states it clicks an element. Doesn't disclose failure behavior, waiting mechanics, return values, or permission needs. References another tool for parameter details but lacks own transparency.

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?

Very concise, two sentences, no wasted words. But brevity sacrifices completeness; reference to 'see click()' is efficient but requires cross-tool lookup.

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?

Despite no annotations and no output schema, description lacks detail on return format, error handling, and behavior for all parameters. Incomplete for a tool with 5 parameters and multiple siblings.

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 0%; description explains 'id' (element id from parse_screen) and references click for 'observe'/'settle_ms', but leaves 'button', 'instance', and 'settle_ms' default undocumented. Fails to compensate for missing schema descriptions.

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?

Description clearly states the tool clicks an element by id from the most recent parse_screen, using a specific verb and resource. Differentiates from siblings like 'click' (no id reference) and 'double_click'.

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?

Implies prerequisite of running parse_screen first ('from the most recent parse_screen'). References 'click()' for observe/settle_ms, but no explicit when-to-use vs alternatives like click, double_click, or drag.

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