load_game_save

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

Adds significant behavioral information beyond the destructiveHint annotation: details on Lua vs OCR loading, time estimates, and file existence check. No contradiction with annotations.

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?

Extremely concise: three short sentences and a bulleted example. Every piece is informative with no fluff. Structure is front-loaded with purpose and usage note.

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?

Missing explicit differentiation from load_save and load_save_from_menu siblings, but output schema exists covering return values. For a simple load tool with one parameter, it is mostly complete.

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 parameter, but the description provides examples of valid save names and explains that the extension should be omitted. This adds critical meaning.

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 'Load a save file by name' with specific verb and resource. It distinguishes from siblings like list_saves and implicitly from other load variants by explaining behavior.

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?

Provides guidance that list_saves is not required first, and explains fallback behavior. Does not explicitly state when to avoid this tool or compare to other load tools like load_save_from_menu, but context is clear.

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