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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing beyond that: it does not warn that a tap can trigger irreversible UI actions, and its only extra content (device pixel coordinates) merely restates the schema.

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 short sentences with the action and the unit front-loaded, zero filler. Nothing to trim without losing information.

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 four-parameter tap with full annotations and complete schema descriptions, the core is adequate. What is missing is workflow context: how to obtain the coordinates and how this differs from android_swipe, which an agent driving a device would need.

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 description coverage is 100%, including the nuanced channel_account_id ambiguity rule and the in_workspace scoping note, so the schema carries the parameter burden. The description's coordinate-unit remark duplicates the x/y descriptions rather than adding meaning, so the baseline 3 applies.

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 names a specific verb (Tap), a target (Android device screen), and the coordinate unit (device pixels), so the agent knows exactly what the tool does. It does not, however, distinguish itself from the closest sibling android_swipe or place itself in the android_* family workflow.

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?

There is no when-to-use guidance: nothing says when to prefer android_tap over android_swipe or android_shell, nor that coordinates typically come from a prior android_screenshot/android_ui_dump. The agent must infer the workflow entirely on its own.

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