press_key

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

No annotations are provided, so the description holds the full burden. It only states the action without any behavioral context (e.g., whether the press is instantaneous, if it waits for completion, how errors are handled, or what the tool returns). This is insufficient for safe invocation.

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 sentence that front-loads the core action and examples. It is concise with no filler, but could be more informative without sacrificing brevity (e.g., explicit note about optional serial).

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 output schema, the description fails to mention return values or side effects. It also omits device prerequisites or behavioral details. The tool is simple but the description lacks completeness for an agent to use it confidently.

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 coverage is 100%, so baseline is 3. The description adds example values for the 'key' parameter (home, back, enter, recents), which provides some context beyond the schema's 'Key name'. However, it does not elaborate on the 'serial' parameter beyond the schema.

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 presses a named key and provides examples (home, back, enter, recents). However, it does not differentiate itself from sibling tools press_back and press_home, which could cause confusion about when to use this generic version vs the dedicated ones.

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 gives no guidance on when to use press_key versus alternatives like press_back or press_home. It fails to mention that this tool is intended for keys without dedicated tools, leaving the agent without decision support.

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