double_click

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

No annotations, so description carries burden. It specifies return structure, failure condition (instance down), and references click() for two parameters. Does not detail side effects or potential destruction, but covers key behavioral aspects.

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?

Extremely concise: three sentences front-load purpose, then return format, then reference and failure. No wasted words.

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?

Adequate for a simple tool: explains action, return, failure, and references for additional detail. Lacks parameter explanations and explicit sibling differentiation, but sufficient as minimal viable description.

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 0%, description does not explain parameters beyond 'absolute pixel coords' for x/y. The observe, instance, and settle_ms parameters are mentioned but not described; refers to click() but no details here. Minimal added meaning.

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?

Clearly states 'Double-click at absolute pixel coords in an instance' with concrete examples like 'open a file icon, select a word'. Distinguishes from sibling 'click' (single click) and 'click_element' (by element).

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?

Provides examples and references click() for observe/settle_ms, but does not explicitly state when to use versus alternatives like click_element or drag. Lacks exclusions or when-not-to-use guidance.

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