tap

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

No annotations provided, so the description carries full burden. It doesn't disclose whether the tap is synchronous, what happens if coordinates are out of bounds, whether serial selection falls back, or what response is returned. Only the coordinate-based nature is conveyed.

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?

Extremely concise and front-loaded: a single clause that states the action and its operand. No wasted words.

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?

Adequate minimum for a simple 3-param gesture tool with no annotations and no output schema. However, for a device-interaction tool it should mention coordinate space, device targeting, and synchronous behavior.

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 33%; only 'serial' is documented in the schema. The description adds no meaning beyond the schema for x/y, but the schema itself already constrains x/y as integers with minimum 0 and documents serial. Baseline 3 for partial coverage where the schema does most of the work.

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?

Clear verb+resource: 'Tap' at 'pixel coordinates'. Distinguishes from sibling tap_element (which likely taps by element selector rather than coordinates), though it doesn't explicitly say so.

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?

No guidance on when to use tap vs tap_element, long_press, or swipe. The sibling tap_element is the obvious alternative and isn't mentioned. Usage is only implied by the name.

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