ui_tap

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

Discloses prerequisite (AXe CLI) and the reliability order of targeting methods. No annotations exist, so description carries the burden; it adequately covers the primary behavioral aspects of the tap action.

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?

Three sentences, front-loaded with the core action, followed by guidance and prerequisite. No wasted words; every sentence earns its place.

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 no output schema, the description sufficiently covers the tool's functionality and the prerequisite. Could explicitly mention the simulator target, but sibling context implies it. Minor gap in not describing return information, but not required.

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 has 100% coverage, but description adds value by explaining the purpose of parameter groups (accessibility id, label, coordinates) and recommending a priority order, surpassing what the schema alone provides.

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 the action ('tap a UI element') and the resources ('accessibility id, label, or x/y coordinates'), distinguishing it from sibling tools like ui_swipe and ui_long_press.

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?

Provides explicit guidance to prefer accessibility id and references ui_snapshot for discovery. Also states the constraint 'at least one targeting method must be provided.' No exclusions or alternatives, but the context is clear.

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