bizhawk_tap

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It doesn't disclose what 'tap' does (press and release a button), how GB-compatibility changes behavior versus emulator_tap, whether there are timing constraints, or what happens on failure. The description adds almost no behavioral context beyond the tool name 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 extremely short (six words and a hyphenated modifier). While brevity is valued, this is under-specification rather than effective conciseness—the description lacks substance. There's no wasted language, but there's also almost no content to evaluate.

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 no annotations, no output schema, and 0% parameter coverage, the description is severely incomplete. The term 'GB-compatible wrapper' hints at an emulator-specific context shared across the bizhawk_* siblings, but it doesn't clarify the tap semantics, frame timing behavior, or how it relates to the emulator_tap parent beyond being a wrapper.

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%, so the description should compensate for the 3 undocumented parameters. It adds zero information about 'button', 'hold_frames', or 'release_frames'—their meanings must be inferred entirely from names and defaults. With 0% coverage and a terse two-word description, this is a significant gap.

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 'GB-compatible wrapper for emulator_tap' indicates this is a Game Boy variant of another tool, but it never states the actual action performed (tapping a button). It relies on the sibling tool name 'emulator_tap' to convey meaning. The verb 'tap' is implied only via the parent tool reference, and 'wrapper' is vague—it doesn't say what the wrapper does differently from the original.

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 bizhawk_tap versus the emulator_tap sibling or the other bizhawk_* tools. The term 'GB-compatible wrapper' vaguely implies it's for Game Boy emulation, but there's no explicit statement about when to choose this tool over alternatives, nor any exclusions or prerequisites stated.

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