key_press

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions 'allowlisted' but gives no information about side effects, permissions, or the role of parameters like allow_power or verify_change. The agent is left without insight into what actually happens when a key is pressed.

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, concise sentence with no redundant words. It efficiently conveys the core action without unnecessary elaboration.

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?

The tool is relatively simple, but with no annotations and no output schema, the description should provide more context about usage, parameter effects, and system impact. The one-liner does not sufficiently prepare an agent to invoke the tool correctly, especially for edge cases like the power key or the purpose of verify_change.

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 schema has zero description coverage, and the tool description does not compensate. It does not explain the meaning of 'key', 'allow_power', or 'verify_change'. The enum on 'key' provides some context, but the other two boolean parameters remain completely ambiguous.

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') and the target ('an allowlisted Android testing key'), and the scope ('allowlisted') implies a constrained set of possible keys. This distinguishes it from sibling tools like ui_tap or screen_swipe, which involve touch interactions.

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. It does not mention any conditions, exclusions, or related tools, leaving the agent to infer usage from the name alone.

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