Click the Linux desktop

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

Beyond the annotations (all false, providing little safety context), the description discloses that the pointer first moves to absolute screenshot coordinates and defaults to a single click. This adds meaningful behavioral context, though details like waiting behavior or output are omitted.

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?

Two concise sentences that front-load the primary action and immediately follow with a key usage detail. Every word adds value.

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?

The core action and coordinate system are covered, but the description does not mention button options, valid count range, or timing behavior. With five parameters and no parameter descriptions, more context would help, though the simplicity of the tool makes it somewhat adequate.

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. It clarifies that x/y are absolute screenshot coordinates and hints at count via the double-click note, but it does not explain count, button, or interval_ms parameters beyond their defaults.

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 tool's action: 'Move to absolute screenshot coordinates and click a mouse button.' The verb 'click' and resource 'mouse button' are specific, and the coordinate context distinguishes it from siblings like move_pointer and drag_pointer.

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 use this tool versus alternatives. The only usage note is about using one click unless a double-click is clearly needed, which addresses count behavior rather than tool selection.

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