Run ROM in headless emulator (libmgba)

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

No annotations provided, so description carries full burden. Reveals output format, optional mid-run screenshot, and setup requirements. Does not detail error handling or stderrTail content.

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?

Two sentences cover launch mechanism, output, retrieval, and setup. No unnecessary words; every sentence 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?

Given no annotations, 4 params, and no output schema, the description is largely complete. Covers output structure, retrieval, setup constraints, and parameter limits. Could add more on error scenarios.

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%, but description adds meaning beyond schema: explains input timeline structure, duration cap, and extra screenshot timing. Provides context for romPath absolute path.

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?

Clearly states it launches a ROM via a scripted runner with input timeline and captures screenshots. Distinguishes from sibling 'screenshot' tool by specifying retrieval method.

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?

Explains when to use (launch ROM with inputs) and provides setup instructions (build runner or set env var). Notes duration cap and suggests splitting for longer walkthroughs, but does not explicitly exclude alternatives.

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