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') but doesn't clarify effects like whether this triggers system shortcuts, requires specific permissions, or has side effects (e.g., opening applications). This is a significant gap for a tool that interacts with the system at a low level.

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 highly concise and well-structured, with a clear purpose statement followed by a brief parameter explanation. Every sentence adds value, and it's front-loaded with the main action, making it efficient for quick understanding without unnecessary details.

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 complexity (interacting with system inputs) and the presence of an output schema, the description is minimally adequate. It covers the basic action and parameter format but lacks details on behavioral traits, error handling, or output interpretation, which are crucial for safe and effective use in this context.

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 adds meaningful context beyond the input schema, which has 0% description coverage. It explains the 'keys' parameter as a combo with examples like 'Ctrl+Alt+t', clarifying the expected format and syntax. This compensates well for the schema's lack of documentation, though it could specify more about valid key names or modifiers.

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 key combination') and specifies the resource (key combinations like 'Ctrl+Alt+t'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'key_press' or 'type_text', which might have overlapping functionality for keyboard input.

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 such as 'key_press' or 'type_text' from the sibling list. It lacks context about scenarios where key combinations are preferred over single key presses or text typing, leaving the agent without usage direction.

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