adb_input_double_tap

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

No annotations provided; description adds value by disclosing 'Two rapid taps with a configurable interval' and mentions triggered effects (zoom, text selection). Could further clarify system vs emulated behavior.

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 concise sentences front-loaded with purpose and a detail sentence. No redundant or irrelevant content.

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 input action without output schema, description covers the action and its effects. Slight omission: it does not explicitly state that coordinates are screen coordinates (inferred from schema).

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 descriptions cover 100% of parameters. Description only adds 'configurable interval' which is already in schema. No additional parameter meaning beyond schema.

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 'Double tap at a point on screen' with specific verb and resource. It distinguishes from sibling input tools like single tap, drag, long press by explicitly naming double-tap gestures (zoom, text selection).

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?

Description implies use for double-tap gestures but provides no explicit when-to-use or when-not-to-use guidance, and does not mention alternatives like adb_tap_element or adb_input_long_press.

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