input.key

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

No annotations are provided, so the description carries full behavioral disclosure. It mentions possible keys but omits crucial context: whether the key injection requires an active unlock state, whether it can turn the device on/off, timing constraints, or what happens if the key is invalid. For a general input tool, this is a significant gap.

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 a single, compact sentence that front-loads the action ('按键注入') and provides the acceptable values. 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?

Given no annotations, no output schema, and incomplete parameter documentation, the description is not sufficient for an agent to use the tool safely and correctly. It lacks details on device state prerequisites, supported key names beyond examples, integer representation, and error behavior.

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 description coverage is 0% and the single parameter 'key' is just typed as string. The description partially compensates by listing example values (back, home, menu, volume_up, volume_down, power, enter) and allowing integer keycodes, but it does not explain the format of integer keycodes or how to combine them.

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 injects key presses, and lists supported key names (back/home/menu/volume_up/volume_down/power/enter) and the integer keycode option. It does not distinguish from siblings like ui.back or ui.home, which cover a subset of these keys, so it loses a point.

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?

No guidance is given on when to use this tool versus dedicated siblings such as ui.back, ui.home, app.launch, or ui.click. The description simply lists valid values.

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