sassy_hotkey

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

The description proactively labels the tool as 'Mutating,' matching the destructiveHint annotation, and discloses that it sends a real keyboard shortcut via pyautogui. It adds important caveats beyond annotations: there is no output validation beyond a confirmation echo, so the agent should verify effects with sassy_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?

The description is compact and front-loaded with the mutation warning, then follows a logical structure: purpose, key syntax, platform support, verification caveat, and sibling routing. Every sentence carries useful information and there is no filler.

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 single-parameter, mutating tool, this description is complete. It covers what the tool does, how to format the parameter, which platforms it supports, what the output reliability is, and when to use alternatives. The presence of an output schema means the return format does not need to be detailed in the description.

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?

The schema only provides a bare 'keys' string with no description, so the description fully compensates by explaining that keys are '+'-separated and by providing multiple valid examples. It also reveals the implementation detail that the string is split and passed to pyautogui, which helps the agent format the input correctly.

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 the exact action—'sends a real keyboard shortcut to the host'—and clarifies the resource being manipulated. Concrete examples like 'ctrl+c' and 'ctrl+shift+s' make the purpose unambiguous and distinguish it from sibling text and mouse tools.

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?

Explicitly tells when to use this tool: 'Use it for shortcuts like save, copy, or window switching.' It also names the alternatives—sassy_type_text for typing text and sassy_click for mouse actions—and even recommends sassy_screenshot for verification when the effect matters.

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