iyke_key

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 clearly explains the combo syntax and targeting behavior. While it does not detail side effects or error handling, the core functionality is transparently described.

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 two sentences, front-loaded with the core action ('Dispatch a keyboard combo'), followed by concise examples and targeting options. Every sentence is informative with no redundancy.

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 simplicity, no output schema, and the presence of sibling tools, the description provides sufficient guidance for correct invocation. It covers the main usage scenario and targeting, though it omits details about the 'pane' parameter and potential errors.

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 input schema has no descriptions (0% coverage), so the description must compensate. It explains the 'combo' parameter format and states that 'ref'/'selector' target an element. However, the 'pane' parameter is not mentioned, leaving one parameter partially undocumented. The description adds value but does not cover all 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 uses the specific verb 'Dispatch' and resource 'keyboard combo', immediately distinguishing it from sibling tools like iyke_type (text input) and iyke_click (mouse click). It provides concrete examples of key names and modifiers, clearly defining the tool's action.

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 explains the combo format and optional targeting, but does not explicitly state when to use this tool versus alternatives (e.g., iyke_type for typing text) or when not to use it. The usage context is implied but lacks explicit guidance on tool selection.

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