desktop_click

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

No annotations provided, so the description carries full burden. It only maps button numbers to mouse buttons but omits side effects (e.g., focus changes), error handling, or out-of-bounds behavior.

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 a single sentence with a clear mapping, avoiding unnecessary words. It front-loads the main action. Could benefit from slightly more detail without becoming verbose.

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 tool with 4 parameters, no output schema, and no annotations, the description is insufficient. It lacks details on coordinate system, return values, error conditions, and preconditions, leaving significant gaps for correct usage.

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?

With 0% schema description coverage, the description adds meaning only for the 'button' parameter via the mapping. The 'id', 'x', and 'y' parameters are not explained beyond their implied roles, leaving ambiguity about coordinate system and identifier usage.

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 verb 'Click' and the resource 'sandbox desktop' with coordinates, distinguishing it from sibling tools like desktop_type or desktop_drag. However, it does not explicitly differentiate from desktop_drag, which also involves clicking.

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 like desktop_drag or desktop_screenshot. Prerequisites (e.g., desktop visibility, coordinate system) are not mentioned.

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