mame_run_frames

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

With no annotations, the description carries the transparency burden. It does disclose the pause side effect and return value, which is helpful. However, it does not mention what happens if the emulator is already paused, if N must be positive, or any error behavior, leaving some gaps.

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 that conveys the action, side effect, and return value without waste. It is well-structured and front-loaded.

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 simple with one parameter, and the description covers the core behavior and return. However, it lacks context about session requirements, whether the tool resumes from a paused state, or interaction with other MAME controls, making it minimally adequate but not complete.

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 already fully describes the parameter 'n' as 'Frames to advance', and the description merely uses 'N' in the same context. Since schema coverage is 100%, the baseline of 3 applies without additional semantic value added.

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 a clear action ('Run N frames'), a specific side effect ('pause'), and the return value ('frame number'). This distinguishes it from sibling tools like mame_pause/mame_resume which do not advance frames.

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 explicit guidance on when to use this tool versus alternatives is provided. The intent is implied by the name and description, but there is no mention of prerequisites (e.g., session running) or comparison to siblings like mame_send_input or mame_capture_game_tick.

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