GNOME Desktop MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('press and release') but doesn't mention important behavioral aspects like whether this simulates a keyboard event, what system context it operates in, potential side effects, or error conditions. The description is minimal and leaves key behavioral traits unspecified.

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 extremely concise and front-loaded with the core purpose in the first sentence. The parameter documentation is brief but informative. Every sentence earns its place with no wasted words or redundant information.

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?

Given the tool's simple nature (single parameter, has output schema), the description is adequate but minimal. With no annotations and a basic input schema, it could benefit from more context about system dependencies, error handling, or practical usage examples. The presence of an output schema reduces the need to describe return values, but more behavioral context would be helpful.

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?

With 0% schema description coverage and only 1 parameter, the description compensates well by providing specific examples of valid key names ('Return', 'a', 'F5', 'Ctrl', 'Escape'). This adds meaningful context beyond the bare schema, though it doesn't provide a comprehensive list or formal specification of allowed values.

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 specific action ('Press and release a single key') and distinguishes it from sibling tools like 'key_combo' (which likely handles multiple keys) and 'type_text' (which likely handles text strings). The verb+resource combination is precise and unambiguous.

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 implies usage for single-key actions, but doesn't explicitly state when to use this vs. alternatives like 'key_combo' or 'type_text'. It provides clear context about what the tool does, but lacks explicit exclusions or comparisons with sibling tools.

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