key_combination

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

No annotations are provided, so the description carries full burden. It discloses that the tool works on focused apps/menus and does not guarantee global hotkeys. This adds important behavioral context, though it could mention prerequisites like app focus.

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 a single, front-loaded sentence with no redundancy. It conveys the essential behavior and limitation without extra words.

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 with 2 parameters and no output schema. The description plus schema adequately convey usage for app/menu key combinations. Minor missing context about needing a focused app is implied but not explicit.

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 100% with both parameters well described. The tool description does not add new parameter-level information beyond reinforcing the context of focused apps, so the schema already carries the burden.

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 presses a key combination with modifiers in a focused app or menu. It distinguishes from sibling tools like press_key (no modifiers) by explicitly including modifiers and from click_menu_item by specifying keyboard vs mouse action.

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 clarifies that OS-global hotkeys are not guaranteed, providing a clear when-not-to-use condition. However, it does not explicitly mention alternatives like press_key for single keys or click_menu_item for menu items.

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