key_press

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

Annotations provide destructiveHint=true, indicating potential side effects. The description does not elaborate on behavior beyond pressing keys (e.g., whether it releases keys, or requires xdotool installed). It does not contradict annotations, but adds minimal transparency.

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 one sentence plus examples, extremely concise with no extraneous information. Every part serves to explain the tool's function and input format.

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 simple one-param tool with no output schema, the description covers core functionality and input format. It lacks mention of dependencies (xdotool) or explicit behavior like key release, but overall is adequate for agent invocation.

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 has 0% description coverage, so description must compensate. It explains that 'combo' uses keysym notation and gives examples, adding meaning beyond the parameter name. However, it could benefit from a more comprehensive list or format specification.

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 keyboard combination using xdotool's keysym notation, with examples. It specifies the verb (press) and resource (keyboard combination), distinguishing it from sibling tools like type_text for typing text, and mouse_* for mouse actions.

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 examples of valid inputs and mentions the notation system, which guides usage. It implicitly differentiates from siblings (e.g., no need for mouse or text typing), but lacks explicit when-not-to-use or alternative tool guidance.

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