computer_double_click

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

The description discloses the coordinate scaling (1429x804 scaled from 1920x1080) but omits details like the timing of the two clicks or any auditory/visual feedback. Without annotations, more behavioral context would be beneficial.

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 extremely concise—two sentences with no extraneous information. Key information is front-loaded.

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 simple tool with two integer parameters and no output schema, the description adequately covers the coordinate system. It is missing any note about the resulting action (e.g., opening a file) but remains largely complete.

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 100% with clear parameter descriptions for x and y. The description adds the scaling context but does not further elaborate on coordinate semantics beyond what the schema provides.

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 explicitly states 'Double-click at the given coordinates,' clearly indicating the action and its target. It distinguishes itself from siblings like left_click and triple_click.

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 provides no guidance on when to use double-click versus alternatives, nor any context about typical use cases (e.g., opening files). It simply states the action.

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