sassy_hotkey

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

With no annotations provided, the description must disclose behavioral traits. It only states the basic action and key format, without disclosing whether the shortcut is sent to the foreground application, whether it requires special permissions, or any side effects. This is a significant gap for a tool that simulates input.

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 two short sentences with no wasted words. The first sentence states the purpose, and the second provides the parameter format. Excellent front-loading and structure.

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?

The tool is simple (one parameter, output schema exists), but the description lacks context such as whether it works globally, requires a focused window, or any limitations. While the example and format are useful, the missing behavioral context makes it incomplete for fully informed use.

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 input schema provides only a 'keys' string with zero description coverage. The description adds crucial format guidance: 'Keys separated by +, e.g. ctrl+c.' This clarifies the required syntax and provides a concrete example. It does not enumerate valid keys, but the format is sufficient for basic usage.

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 action ('Press keyboard shortcut') and the resource ('keyboard shortcut') with an example. It distinguishes from siblings like sassy_click (mouse) and sassy_type_text (typing text) by focusing on key combinations using '+'. However, it doesn't explicitly mention 'simulate' or 'send to active window', which could add precision.

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 no guidance on when to use this tool versus alternatives. There is no mention of context (e.g., 'use for global hotkeys' or 'for typing text use sassy_type_text'). The example implies usage for shortcuts, but no explicit when-to-use or exclusions are given.

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