long_press

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

With no annotations, the description carries the burden. It states a coordinate-based press and provides use cases, but doesn't disclose details like whether it validates coordinates or that duration_ms controls the press length. It is not misleading, just minimal.

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?

The description is two sentences with the action front-loaded. Every word serves a purpose—no fluff.

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 4-parameter tool with no parameter descriptions and no annotations, this description is too sparse. It lacks guidance on coordinate origin, duration defaults, and how it differs from tap. The use-case examples are useful but insufficient.

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 0% and the description adds no parameter details. It mentions 'coordinates' but doesn't explain x/y semantics, device usage, or duration_ms default. The agent gets no help understanding parameters beyond their names.

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 clearly states 'Long press at coordinates' with a specific verb and resource, and provides examples of use cases. It distinguishes from siblings like tap_element by focusing on the long-press gesture, though it doesn't explicitly name alternative tools.

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?

The description explicitly mentions when to use it: 'for context menus, drag initiation, etc.' This gives clear context but doesn't provide exclusions or mention alternatives like tap for simple clicks.

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