press_keys

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

Annotations are all false/unhelpful, and the description does not disclose important behavioral traits such as the possibility of focus disruption, background key delivery, the need for user confirmation, or the AutoHotkey fallback behavior. The only behavioral addition is that multiple keys are pressed together and confirmation is returned, which is minimal.

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 well-structured: a one-sentence purpose, a usage note, an Args section, and a Returns section. Every sentence contributes meaningful information without fluff.

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?

Despite a rich nested schema, the description is too thin for a complex tool with optional background targeting, focus-confirmation requirements, and platform-specific display settings. It does not explain when or how to use these options, nor does it contextualize the tool among its many siblings. The output schema spares return-value detail, but behavioral context is missing.

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 description mischaracterizes the 'params' argument as a 'list of pyautogui key names', when it is actually a HotkeyInput object with additional fields (hwnd, display, prefer_ahk, window_title, confirm_focus_disruption). It adds useful list semantics but may mislead an agent into omitting the object wrapper or ignoring all optional parameters.

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 a keyboard combination') with concrete examples (Ctrl+C, Alt+Tab) and the resource (keyboard). It is specific and unambiguous, though it does not explicitly differentiate this from sibling tools like win_send_keys or ahk_control_send.

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 gives basic input semantics (single vs. multiple keys) but provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. For example, it does not mention when background delivery (hwnd/window_title) might be appropriate or when confirm_focus_disruption is required.

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