sassy_click

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

No annotations are provided, so the description carries the burden. It adds useful context by specifying 'absolute screen coordinates' and 'works across multiple monitors', but does not disclose potential side effects like focus stealing or required accessibility permissions.

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 action and provide necessary guidance. Every word earns its place with no redundancy.

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, the description is reasonably complete: it specifies coordinate system, multi-monitor support, and a prerequisite. With an output schema present, return values are not needed, but it could mention coordinate origin or button defaults.

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%, and the description only explains 'x' and 'y' implicitly as coordinates. It does not explain the 'button' or 'clicks' parameters, leaving them ambiguous without schema descriptions.

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 function: 'Click at absolute screen coordinates' – a specific verb and resource. It also distinguishes itself from sibling tools like sassy_type_text and sassy_hotkey by focusing on clicking at coordinates.

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 description provides explicit guidance to 'Use sassy_screen_info to find monitor positions first', which is a clear prerequisite. It implies usage context for clicking at coordinates but does not mention alternative tools for other input actions.

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