Long Press

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

No annotations are provided, so the description carries full burden. It discloses that the tool performs a long press which can trigger context menus, drags, or secondary actions, but does not mention any side effects, prerequisites (e.g., element must be present), or system behavior. It does not contradict annotations (none given).

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 (two sentences) and front-loaded with the action. It efficiently conveys purpose and common use cases without waste.

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 tool is a simple gesture with parameters fully described in schema, the description is adequate. However, it lacks information about return values, error conditions, or system behavior, which would be helpful for completeness.

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%, so baseline is 3. The description does not add parameter-level details beyond the schema. It mentions coordinates and duration in the context of use cases, but the schema already documents them adequately.

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 explicitly states the tool performs a 'long press (touch and hold)' at given coordinates, with clear purpose: opening context menus, starting drag operations, or triggering secondary actions. The verb 'Perform a long press' and resource 'screen coordinates' are specific, and the examples distinguish it from other gestures like double_tap or swipe.

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 mentions common use cases but does not explicitly state when to use this tool versus siblings like tap, double_tap, or swipe. It implies usage through examples but lacks clear guidance on when not to use it or alternatives.

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