ui_keystroke

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

No annotations exist; description fails to disclose behaviors such as whether focus on a specific page is required, potential UI side effects, or if it works in all contexts. The example implies 'Edit page' but not explicit.

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?

Two sentences with an example; compact and front-loaded. Could be slightly more structured (e.g., separate example), but no wasted 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?

Lacks output schema and provides no return info; no prerequisites or context about when to use. Given low complexity (2 params), it is minimally adequate but not thorough.

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% coverage; description adds meaning by explaining keys parameter with a concrete example and listing possible modifier values, going beyond the schema's empty descriptions.

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?

Description clearly states the tool sends a keyboard shortcut to Resolve, with example and modifiers. Differentiates from siblings like ui_menu_click by specifying 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?

Provides example usage (Add Marker shortcut) and lists modifiers, but does not specify when to use this vs. alternative tools (e.g., ui_menu_click) or when not to use it.

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