click_mouse

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Click' without explaining that a click involves pressing and releasing a button, potential side effects like focus changes, or that doubleClick toggles a double-click. This is a significant gap.

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 concise sentence, but it is under-specified. It omits essential details that an agent needs to call the tool correctly. While brevity is good, this description is so short that it fails to earn its place by conveying necessary information.

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 and no output schema, the description is severely incomplete. An agent needs to know that coordinates are screen-relative, that doubleClick toggles a double-click, and the meaning of each button option. With no annotations to supplement, this is inadequate.

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 explain parameter meanings. It does not describe x and y coordinates (e.g., screen-relative, units), the button enum options, or the doubleClick boolean. The only hint is 'selected mouse button', which vaguely refers to the button parameter but adds no real value.

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 states a specific verb ('Click') and resource ('screen coordinate'), and clarifies it uses a mouse button. This clearly distinguishes it from siblings like move_mouse (no click) and press_key (keyboard action). The purpose is unambiguous even without explicit differentiation.

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. It doesn't mention typical use cases (e.g., clicking UI elements) or that move_mouse should be used for positioning without clicking. There are no exclusions or conditions provided.

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