ui_click

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

Annotations provide openWorldHint=false, and the description adds caching and fallback details. No contradictions. However, the description does not disclose other behaviors like side effects, error handling, or waiting conditions beyond what is implied.

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 concise with a clear header, note, and explanation. It uses bullet points for parameters, which aids readability. No unnecessary sentences.

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 tool has 5 parameters with no schema descriptions, no output schema, and moderate complexity. The description fails to cover all parameters, does not explain return behavior, error cases, or preconditions beyond the breakpoint note. This leaves the agent under-informed.

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?

The description explains 3 of 5 parameters (automation_id, name, control_type), but omits root_id and xpath entirely. Given 0% schema description coverage, the description partially compensates but leaves significant gaps.

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 'Click on a UI element', which is a specific action on a specific resource. The name 'ui_click' and siblings like 'ui_double_click', 'ui_right_click', 'ui_click_annotated' help distinguish it.

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 includes a note about resuming execution if app is stopped. It also explains the caching and fallback behavior, providing implicit guidance on when this tool is appropriate. However, it does not explicitly contrast with sibling tools or state when not to use it.

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