bizhawk_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. The description doesn't state effects, side behaviors, or what the save operation captures. A save-state tool's behavioral footprint is entirely undisclosed.

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 short sentence, extremely concise, but this is under-specification rather than effective conciseness since it provides almost no 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 stateful save operation with one parameter, zero annotations, zero output schema, and 0% schema coverage. The description adds essentially nothing, leaving the agent without critical operational 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% for the single 'name' parameter, and the description adds zero parameter context. What 'name' represents and its constraints are entirely unexplained.

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 it's a 'GB-compatible wrapper for emulator_save_state,' implying it saves state, but it relies on understanding of the sibling tool. It doesn't state the verb+resource directly or differentiate meaningfully from emulator_save_state or bizhawk_load_state.

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 when-to-use or when-not-to-use guidance is provided. It doesn't explain when to choose this GB-wrapper over the plain emulator_save_state or how persistence/recovery works.

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