long_press

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

No annotations are provided, so the description carries the behavioral-disclosure burden. It states the default hold duration and common effects, but omits verification behavior, polling/timeout semantics, and any risk or mutating side-effect profile.

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 short sentences, front-loaded core action, then effects, then sibling alternative. Every sentence earns its place with no wasted text.

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?

Core invocation and sibling routing are covered, but with no output schema and no annotations the description leaves verification parameters and result/return behavior unexplained. The schema partially compensates for optional parameter 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 67%. The description names x, y and repeats the duration_ms default, but does not add meaning for verify, verify_poll_ms, or verify_timeout_ms beyond what the schema descriptions already provide.

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?

States the specific verb 'long-presses' with coordinate and duration inputs, describes intended outcomes (context menus, text selection, drag grab), and names the sibling for element targets. An agent can distinguish it from long_press_element and other gesture tools without opening the schema.

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?

Gives clear use cases (context menus, text selection, dragging) and explicitly routes element-target use to long_press_element. It does not cover prerequisites or when coordinate long press should be preferred over other siblings like swipe or tap beyond the element alternative.

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