emulator_tap

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

No annotations are provided, so the description carries full burden. 'Neutral frames before and after' gives some behavioral context (the action is framed by idle frames), and the default hold/release frame parameters imply timing behavior, but it doesn't disclose what happens on failure, whether a device must be initialized, or side effects. The parameter defaults partially communicate the press-and-release timing but are not part of the description itself.

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 efficient sentence with zero waste. It's appropriately short but perhaps underspecifies for a tool with 4 unchecked parameters.

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?

For a tool with 4 parameters, 0% schema coverage, no annotations, no output schema, and many closely-related siblings (hold, release, press, tap across emulator and bizhawk namespaces), the description is far too thin. It doesn't explain parameter semantics, target default meaning, how it differs from emulator_hold/release, or what state is affected. The neutral-frames mention is the only meaningful depth.

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 there are 4 parameters (button, target, hold_frames, release_frames) with no enum constraints. The description adds no meaning to any parameter—'Tap one button' only implies 'button' is the one being tapped. With zero coverage and no description support, parameters like target (default 'gb' meaning Game Boy) and hold/release frames are completely unexplained.

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 states 'Tap one button' which identifies the verb and resource, but does not specify what this does in emulator terms (press and release a button briefly). It doesn't distinguish from siblings like emulator_hold, emulator_release, or bizhawk_tap—the purpose is clear only in the most basic sense.

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 on when to use tap vs hold vs release. Given the sibling set includes emulator_hold, emulator_release, and bizhawk_tap, the description provides no context for choosing among these alternatives. The mention of 'neutral frames before and after' hints at usage timing but doesn't explain why or when that matters.

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