load_save

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

Annotations include destructiveHint=true. Description adds valuable behavioral context: 'The game will reload entirely' and a warning about waiting 10 seconds, which goes beyond the annotation to inform the agent of side effects.

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 extremely concise: two short paragraphs, each sentence adds essential information. No fluff or repetition.

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 is destructive (load game), has one parameter, and output schema exists (assumed to document returns), the description covers input semantics, side effects, and recommended follow-up action. Complete for safe invocation.

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 0% description coverage for the single parameter 'save_index'. The description fully compensates by explaining it is 'Index number from list_saves output (1-based)', giving clear meaning and source.

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 explicitly states 'Load a save file by index from the most recent list_saves() result.' It uses a specific verb and resource, and distinguishes from sibling tools like load_game_save and load_save_from_menu by specifying the source.

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 when-to-use (after list_saves) and post-usage guidance ('wait ~10 seconds, then use get_game_overview to verify'). It also explains the parameter format (1-based index).

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