mame_load_state

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

With no annotations, the description carries the full transparency burden. It discloses a prerequisite (stateDirectory) and a follow-up action (run_frames), which adds useful context beyond the tool name. However, it does not detail side effects (e.g., overwriting current state) or failure modes, leaving some behavioral ambiguity.

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 two short sentences, front-loaded with the core purpose. The parenthetical 'needs stateDirectory' and the follow-up instruction are concise and necessary, earning their place without waste.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential context: what it does, a prerequisite, and the next step. It is adequate for an agent to invoke the tool correctly, though it omits edge cases like error handling or state overwriting.

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?

The schema has only one parameter 'name' with no description (0% schema coverage). The description's phrase 'by name' clarifies that the parameter is the identifier for the save state, which is the essential semantics. It does not add details like name format or where to find valid names, but it is sufficient for a simple string parameter.

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 clearly states the tool's function: 'Load a MAME save state by name.' It uses a specific verb ('Load') and resource ('MAME save state'), and is easily distinguished from siblings like mame_save_state (save) and mame_run_frames (run).

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 clear usage context: it mentions the need for 'stateDirectory' and instructs to 'Apply with a run_frames after.' This gives the agent an explicit sequence to follow, though it does not explicitly name alternatives or exclusions.

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