computer_double_click

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

With no annotations, the description carries the burden of behavioral disclosure. It does clarify that the click uses the left button and is at absolute screen coordinates, and that it returns a JSON response. However, it does not mention potential side effects, coordinate origin, or multi-monitor behavior, leaving some ambiguity for a UI-mutation 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 and well-structured: one sentence for the action, then clear Args and Returns sections. Every line earns its place with no redundant 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?

For a relatively simple tool, the description fully documents parameters and return type. It is missing some usage context around coordinate system details and alternatives, but the essential information for calling the tool correctly is present.

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%, so the description is the only source of parameter meaning. It adequately explains all three required parameters: serialno comes from list_devices, x is in screen pixels, and y is in screen pixels. This is clear and useful, though it could add coordinate origin or bounds details.

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 states a specific action ('Double click'), a resource ('absolute screen coordinates'), and the button ('left button'), which clearly distinguishes it from single-click or long-click siblings. It adds meaningful detail beyond the tool name.

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 does not provide guidance on when to use this tool versus alternatives like computer_click or computer_long_click. It only explains the parameters, not the selection context or exclusions.

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