ui_long_press

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

With no annotations, the description fully bears the burden of behavioral disclosure. It only describes the basic action but omits details like what happens on execution (e.g., gesture completion, timing, error behavior). The prerequisite is noted, but agent-impacting behaviors like potential side effects are absent.

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 at three sentences, each serving a distinct purpose: action, workflow hint, and prerequisite. It is front-loaded with the core purpose. Minor improvement would be separating the prerequisite more explicitly.

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 the simplicity of the tool and lack of output schema, the description provides basic completeness: what it does, how to get coordinates, and a prerequisite. However, it misses behavioral context (what happens during/after the gesture) and return value info, making it adequate but not thorough.

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%, meaning the input schema already describes all parameters. The description adds no further semantic value for any parameter (e.g., coordinate format, duration range). Thus, the baseline score of 3 is appropriate.

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 action ('long press (touch-and-hold)') and the target ('on the simulator'), making the purpose immediately clear. However, it does not distinguish this tool from sibling tools like ui_tap or ui_swipe, preventing a higher score.

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 provides guidance on when to use ui_snapshot to get coordinates, implying a typical workflow. It also mentions a prerequisite (AXe CLI installation). However, it lacks explicit when-not-to-use instructions or alternatives, leaving the agent to infer usage context.

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