computer_long_click

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

No annotations are present, so the description carries the burden of behavioral disclosure. It explains the press-and-hold action, the duration parameter semantics, the default behavior for duration, and the JSON return type. It does not mention pointer movement or button release, but these are minor for a simple input tool.

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 compact, starts with a direct action sentence, and uses a clean Args list with definitions and units. No filler or redundant content.

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?

All required parameters are described, units are specified, the return type is noted, and an output schema exists, so nothing essential is missing. It only lacks additional context such as coordinate origin or behavior on invalid coordinates, which are minor for this tool.

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 0%, but the description fully compensates by explaining all four parameters: serialno's source, x/y as screen pixel coordinates, duration in seconds, and the omit-or-zero default behavior. This goes well beyond the schema titles.

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 the action: 'Press and hold the left button at the coordinates.' This is a specific verb phrase with a clear resource and distinguishes it from computer_click, double_click, and mobile_long_press by emphasizing 'hold'.

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 explicit guidance is given about when to use this tool versus alternatives like computer_click or mobile_long_press. The only contextual hint is that serialno comes from list_devices, but there are no exclusion criteria or selection guidance.

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