press

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the core behavior of pressing and releasing, and that a frame may optionally be returned after the action. However, it does not address timing precision, key event semantics, side effects, permissions, or success behavior.

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?

A single tight sentence, front-loaded with the core operation and examples. Every phrase earns its place.

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?

Without annotations or an output schema, the description should compensate more. It does not clarify parameter semantics (hold_ms, snapshot_after_ms), return behavior, or when to prefer this over hold or sequence, leaving significant gaps for an input tool with three parameters.

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 0% and none of the three parameters are described in the schema. The description does not explain hold_ms (the press duration) or snapshot_after_ms (delay before optional frame capture), leaving most parameter meaning undocumented. Only the button parameter is touched via examples.

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?

States a specific verb (press and release) and resource (one button), with examples of valid button values. It is distinguishable from sibling tool hold (press-hold), release_all (release only), and sequence, but does not explicitly name these distinctions.

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?

Implies use for momentary button presses by the name and description, but gives no explicit when/when-not guidance or direction to alternatives like hold, release_all, or sequence.

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