double_click

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

No annotations, so the description carries the full behavioral burden, and it is thin. It does not disclose the coordinate origin (screen vs. last screenshot), timing between the two clicks, or that 'screenshot_after' defaults to true and triggers a capture. No mention of side effects such as focus/selection changes.

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?

A single tight sentence with the action front-loaded and no filler. It is efficient, but the brevity shades into under-specification rather than true conciseness.

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?

With no annotations, no output schema, and 0% parameter coverage across 3 parameters, the description leaves key details (coordinate frame, screenshot_after behavior, interaction with the current UI state) unspecified. Inadequate for a GUI-automation primitive where ambiguous coordinates cause wrong clicks.

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 must compensate but only partially does. 'in the last screenshot' loosely implies x/y are in screenshot-relative pixel space, but the third parameter 'screenshot_after' is never mentioned and the coordinate frame remains ambiguous.

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 a concrete action (double-click) plus the target coordinates and the surface it acts on ('last screenshot'). This is clearly distinguishable from the sibling 'click' by the double-click semantics, though the description never explicitly contrasts them.

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 prefer this over 'click', 'menu', or 'set_field', and no prerequisites given. The agent must infer from the tool name alone that this is the two-click variant.

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