emulator_save_state

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. 'Save' implies a write operation, but the description doesn't clarify whether the operation is destructive to existing saves, whether it overwrites prior states with the same name, whether it requires an active emulator session, or what side effects occur. It does convey the key action (saving state), but omits side effects and prerequisites.

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 efficient sentence with no wasted words. It is appropriately brief, though this brevity comes at the cost of missing useful context that completeness scores penalize.

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 mutation tool with zero annotations, zero schema description coverage, two fully-undocumented parameters, no output schema, and a large sibling set with overlapping functionality, this description is insufficient. The agent has no information about 'target' semantics, save name behavior, overwrite behavior, or how this differs from the bizhawk_save_state sibling. A mutation tool with this much ambiguity should provide more context.

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 description provides no parameter details at all. The 'name' parameter (default 'state') and 'target' parameter (default 'gb') have no explanation in either the schema or the description - the meaning of 'target' in particular is ambiguous (is it a file type, a device, a path?). The description adds zero parameter-level value beyond the schema's defaults and names.

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 ('Save a BizHawk state') with a specific resource (target runtime states directory). However, it doesn't distinguish it from sibling tools like bizhawk_save_state, emulator_load_state, or emulator_create_baseline - the purpose is clear but not differentiated from closely related siblings.

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?

There is no guidance on when to use this tool vs alternatives. With siblings like emulator_load_state, emulator_create_baseline, bizhawk_save_state, and emulator_run_scenario present, the absence of any when/when-not guidance is a notable gap. The description provides no context for choosing this over the bizhawk_-prefixed versions or other emulator_ state tools.

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