Tap UI Element by Text

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

Annotations (readOnlyHint=false) indicate mutation; description confirms tapping. Discloses regex partial match and center tapping. Does not detail failure behavior or timeout beyond wait_ms. No contradiction with annotations.

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, no extraneous text. Front-loaded with core action and constraint.

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?

Captures core functionality but lacks details on error states (element not found, multiple matches), scope (current UI tree), and does not explain return value (no output schema). Adequate for simple tool but could be more complete.

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?

All parameters have schema descriptions (100% coverage), but the description adds 'Regex partial match' (which is slightly different from schema's 'case-insensitive partial match') and 'tap its center', providing behavioral context 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?

Clearly states it finds a UI element by text/ID/content-desc using regex partial match and taps its center. Distinguishes from siblings like adb_tap (coordinate tap) and adb_text (text input).

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?

Implies usage for tapping elements by text but does not explicitly state when to use it vs alternatives like adb_tap for coordinates or adb_ui_tree for inspection. No when-not or conditional guidance.

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