longpress

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

With no annotations, the description carries full behavioral disclosure burden. It only says 'Long press', which is vague. It does not explain what happens during or after the long press (e.g., gestures, context menus), nor does it mention side effects, permissions, or that the durationMs parameter controls hold time. The output schema is present but not referenced.

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 very concise (single sentence) but under-specified for a tool with 27 parameters and many siblings. It is not structured—no sections, examples, or grouping. While brevity is good, this lacks sufficient detail to be optimally helpful.

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 the high parameter count (27), the presence of output schema, and many sibling tools like 'press', 'click', and 'gesture', the description is too minimal. It does not clarify how longpress differs from these siblings, nor does it explain the purpose of key parameters like durationMs, platform specifics, or target resolution details.

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%, so baseline is 3. The description adds no additional meaning beyond the schema; it only repeats the targeting methods already detailed in the 'target' parameter. Key parameters like durationMs are not mentioned.

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 'Long press by ref, selector, or point.' clearly states the action (long press) and the three targeting methods. This differentiates it from sibling 'press' and 'click' by specifying 'long', but it does not explicitly contrast with other gesture tools like 'gesture' or 'swipe'.

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 longpress versus alternatives like 'press' or 'click'. The description does not mention the duration parameter (durationMs) or any prerequisites. It fails to indicate that this tool is for press-and-hold actions typically used to trigger context menus or special interactions.

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