bizhawk_load_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 adds nothing about behavior—no mention of what 'GB-compatible' means in practice, whether loading a state is destructive, what safety considerations apply, or how the behavior differs from the wrapped tool. For a state-loading operation, this is a significant 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 short sentence, which is concise, but it's under-specified rather than efficiently concise. It conveys minimal information without being verbose. Technically no wasted words, but the brevity borders on insufficient rather than well-crafted.

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?

With no output schema, no annotations, and 0% parameter coverage, the description should provide substantial context. It provides almost none beyond deferring to emulator_load_state. The term 'GB-compatible' hints at wrapped tooling but the agent gets no information about semantics, requirements, or relationship to the parent tool.

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?

There is only 1 parameter (name), and the schema description coverage is 0%, so the description should compensate. The description doesn't explain what 'name' refers to—presumably a save state name—but doesn't say. With a single simple string parameter, the baseline is moderate; the lack of any description for the parameter limits it to a 3.

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 'GB-compatible wrapper for emulator_load_state.' The verb+resource is implied (loads a state), and it references the parent tool emulator_load_state, which provides context. However, it doesn't explicitly state what it does—it relies on the reader knowing what emulator_load_state does. It does distinguish itself from the sibling emulator_load_state by noting it's a GB-compatible wrapper, but lacks a clear standalone statement of purpose.

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 provides no guidance on when to use this tool versus alternatives. It mentions it's a 'GB-compatible wrapper' but doesn't explain when GB compatibility matters, when to prefer this over emulator_load_state, or any caveats. No exclusions or context about the relationship between the bizhawk_* wrappers and the emulator_* originals.

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