mouse_click

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

Description explains movement behavior and uses 'click' appropriately. Annotations include destructiveHint: true, and description does not contradict. However, it does not elaborate on potential consequences beyond the annotation.

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 sentences, no fluff, front-loaded key information. Every word earns its place.

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 click tool with 3 optional parameters, the description covers the core behavior (click, optional move, default button) and no output schema is needed. Complete for the task.

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 only 33% schema description coverage, the description adds essential context for x and y parameters, clarifying that they trigger movement before clicking. Button parameter is sufficiently described in schema.

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?

Description clearly states 'Click a mouse button' and explains conditional behavior with coordinates, distinguishing it from siblings like mouse_move and mouse_drag.

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?

Description implies use case: clicking with or without coordinate movement, but does not explicitly contrast with sibling tools like mouse_drag (which involves dragging) or mouse_scroll.

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