emulator_load_state

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether loading overwrites current emulator state, whether the target emulator must be running, what happens on failure (missing state file), or whether this affects the running game session. For a state-mutation operation, this is a meaningful 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 wasted words. However, it is arguably under-specified rather than concise — while it has a clean structure, it lacks sufficient content to be genuinely useful. It's borderline between appropriate brevity and inadequate detail.

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 2-parameter tool with 0% schema coverage, no annotations, and no output schema, the description is too thin. It does not clarify the state file naming convention, the target values supported, failure behavior, or how this relates to the many sibling save/load tools. A more complete description is needed given the lack of structured metadata.

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 two undocumented parameters (name and target). It does not explain what 'name' refers to (a file name? a key?), nor what 'target' values are valid ('gb' is the default but no enum or list of options is given). The description adds no parameter meaning beyond what the bare schema provides.

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 specific verb+resource ('Load a BizHawk state from the target runtime states directory'), clearly indicating this is a state-loading operation. However, it doesn't distinguish itself from sibling tools like emulator_load_baseline, bizhawk_load_state, or bizhawk_load_baseline, which appear to serve similar functions.

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 guidance is provided. There is no indication of when to prefer this over emulator_load_baseline or the bizhawk_* equivalents, nor any context about the relationship between the 'runtime states directory' and other state sources. The description leaves the agent to infer usage context.

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