adb_input_long_press

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

The description discloses the implementation detail (zero-distance swipe with configurable hold duration) and the behavioral outcomes (context menus, drag handles). Given no annotations, it provides sufficient transparency beyond mere action, though it does not mention prerequisites like screen-on state.

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 sentences with no redundant information. Every sentence earns its place, covering action, effects, and implementation in a compact format.

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?

For a simple single-gesture tool, the description provides complete context: what it does, what it triggers, how it works. No output schema is needed as the behavior is self-explanatory.

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 adds value by explaining the underlying mechanism (zero-distance swipe) and the purpose of the duration parameter, enhancing understanding beyond the schema's basic coordinate and duration definitions.

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), the resource (screen coordinates), and the effects (triggers context menus, selection mode, etc.). It effectively distinguishes this tool from siblings like adb_input_tap or adb_input_drag by specifying 'long press' and its behaviors.

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?

While the description implies usage scenarios (context menus, selection mode), it does not explicitly state when to use or avoid this tool vs alternatives like adb_input_double_tap or adb_input_drag. No direct comparison or exclusions are provided, leaving the agent to infer from context.

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