emulator_gb_gpu_snapshot

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. It does mention 'raw' dump and 'diagnostic PNG panels' which hints at behavior, but it doesn't disclose side effects (e.g., whether files are written to disk, whether output_dir is required for PNG generation, whether this is a read-only operation). For a diagnostic dump tool with zero annotation coverage, more transparency about outputs and side effects is needed.

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?

Single concise sentence with the two core behaviors (dump + render). It's front-loaded and there's no wasted verbiage. Could arguably be a bit under-specified rather than over-specified, but for what it conveys, it's compact.

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?

No annotations, no output schema, 5 parameters at 0% description coverage, and a near-identical sibling tool (gb_gpu_snapshot). This is a moderately complex diagnostic tool that needs to explain what raw GPU data includes, where output files go, relationship to the sibling snapshot tool, and parameter behavior. The current single sentence is inadequate for an agent to invoke this correctly and understand its output.

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 must compensate for the 5 parameters. It only explains the overall behavior (dump raw data, render PNGs) but doesn't explain what 'name', 'render', 'target', 'output_dir', or 'include_raw' individually do. Basic semantics can be inferred (render controls PNG generation, include_raw controls raw dump, output_dir for file location), but the description does not explicitly clarify these, leaving ambiguity.

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 says 'Dump raw GB DMG GPU data and optionally render diagnostic PNG panels.' This gives a reasonably clear purpose (dump GPU data + optionally render PNGs). However, it does not distinguish this from the sibling sibling 'gb_gpu_snapshot' tool, which likely does something very similar. The tool name adds 'emulator_' prefix but the purpose overlap with gb_gpu_snapshot is not addressed.

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 this tool instead of its near-duplicate sibling gb_gpu_snapshot, or versus other emulator_* inspection tools. There's no mention of debugging scenarios, when rendering panels is appropriate, or relationship to the other GPU snapshot tool. Usage context is entirely implicit.

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