sassy_click

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

Annotations already indicate destructiveHint=true; the description adds that it is 'Mutating', performs a 'real mouse click', uses absolute coordinates across all monitors, and works cross-platform via pyautogui. This is meaningful context beyond the annotations, though it could have noted potential side effects like moving the cursor or focusing windows.

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?

Four sentences deliver the essential behavior, parameter semantics, coordinate caveat, prerequisite, and sibling alternatives with no wasted words. The opening 'Mutating' immediately signals the tool's nature.

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?

Given the simple schema, destructiveHint annotation, and presence of an output schema, the description fully covers what the tool does, how to use it correctly, and when to prefer alternatives. An agent can invoke it without external documentation.

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 carry parameter meaning. It explains x/y as required absolute screen coordinates, button options ('left' default, also 'middle', 'right'), and clicks semantics (default 1, for double-clicks and beyond). All four parameters are meaningfully described.

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 and resource ('performs a real mouse click on the host desktop') and explicitly contrasts with sassy_hotkey and sassy_type_text, so the agent can distinguish this tool from its siblings without opening schemas.

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?

Provides explicit when-to-use ('Use it for clicking GUI elements'), identifies alternatives ('use sassy_hotkey for keyboard shortcuts and sassy_type_text for entering text'), and recommends a prerequisite call to sassy_screen_info or sassy_desktop_state for coordinates. This is complete routing guidance.

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