click

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

With no annotations, the description carries the full behavioral burden. It does not disclose whether the click blocks, what happens on failure, whether a new screenshot is captured (the schema's screenshot_after default of true is unexplained), or whether coordinates are absolute pixels in the prior screenshot.

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 tight sentences with the action and coordinate target front-loaded, followed by the optional modifier semantics. No filler; every clause carries 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?

A simple 5-parameter tool with no annotations and no output schema needs the description to cover coordinate semantics and the side effect of screenshot_after. Two of the five parameters are well covered, but the unstated coordinate origin and unconditional post-click screenshot behavior leave real gaps.

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 usefully documents the button enum (left/right/middle) and modifiers with a concrete example ['command'], but leaves x/y coordinate space and the screenshot_after parameter (default true) entirely undefined.

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?

States a specific verb (click) and the exact target (x, y coordinates in the last screenshot), which is precise enough to invoke. It implicitly differentiates itself from sibling double_click and drag by naming a single click, but does not explicitly contrast with them.

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?

The phrase 'in the last screenshot' implies a prerequisite (a screenshot must exist) but gives no explicit when-to-use guidance or routing against siblings like double_click or menu. Usage is inferable from the mouse-action family but not stated.

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