bizhawk_screenshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Yet it discloses nothing beyond being a 'wrapper' — no detail on output format, file location, side effects, failure modes, or differences from the underlying emulator_screenshot. For a screenshot tool that presumably writes a file, this is a major transparency gap.

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 with no waste. However, it is under-specified rather than simply concise — 'GB-compatible wrapper for emulator_screenshot' is short but leaves the agent to infer essentially all behavioral specifics. Conciseness alone is not an asset when it omits crucial information.

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?

This is a screenshot tool with no annotations, no output schema, and 0% schema description coverage. The description says only that it's a 'GB-compatible wrapper' without explaining the GB compatibility aspect, the screenshot naming/output behavior, or when to choose it over emulator_screenshot and emulator_gb_gpu_snapshot/gb_gpu_snapshot. Completely inadequate for an agent to select and invoke it correctly.

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 the single parameter 'name' (default 'shot') is not described in the description text. However, with only one optional simple string parameter with a sensible default, the schema largely self-documents it. The description adds nothing about naming conventions or file type, but the low complexity keeps this at baseline.

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_screenshot' conveys that this tool takes a screenshot with Game Boy compatibility, and correctly references the parent tool. However, it doesn't state what the wrapper specifically changes (e.g., format, color profile) or what distinguishes it from the many bizhawk_* and emulator_* siblings besides the GB-compatibility note.

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?

The description implies usage for Game Boy-related screenshots but provides no explicit when-to-use guidance or exclusions relative to emulator_screenshot or the other emulator/bizhawk siblings. It doesn't tell the agent when to prefer this over emulator_screenshot or how it differs, which is important since both exist as siblings.

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