load_save

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

The description discloses that the game will reload entirely and provides a wait time and post-load verification step. This adds significant behavioral context beyond the destructiveHint annotation.

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 concise with three short paragraphs, each serving a clear purpose: the action, the parameter, and the behavioral guidance. No redundant 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?

Given the destructive nature (destructiveHint: true), the explanation of game reload and recommended follow-up with get_game_overview makes the description complete. An output schema exists but the description appropriately references verification separately.

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 description explains that save_index is 1-based and comes from list_saves output. This adds crucial meaning beyond the input schema, which only specifies the type as integer. With 0% schema coverage, the description fully compensates.

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 verb 'load', the resource 'save file', and the method 'by index from the most recent list_saves() result'. This distinguishes it from siblings like 'load_game_save' and 'load_save_from_menu'.

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 context on when to use the tool (after list_saves) and what to do after (wait and verify). However, it does not explicitly state when not to use it or provide alternatives among the sibling tools.

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