Save the game

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

Discloses critical crash risk for heavily-scripted mods with a concrete example. Without annotations, this is valuable behavioral context, but lacks details on what happens during save (e.g., overwriting, file location).

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: one short sentence plus a focused note. Every word adds value; no redundancy.

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?

Despite low complexity, the description omits parameter details and does not explain return values or success/failure behavior. The crash warning is helpful but not sufficient for a 3-parameter tool with no output schema.

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?

With 0% schema description coverage, the description must explain parameters but does not mention any of the three parameters (name, instance, description). The sole instruction 'Run `save`' provides no parameter guidance.

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?

Description states 'write a savegame' and restricts to single-player/cooperative only, making the core action clear. However, it doesn't explicitly distinguish from sibling tools like load_game or list_saves beyond the action.

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?

Implies use for saving games and excludes multi-player, but provides no explicit alternatives or when-not-to-use guidance. The crash warning adds context but does not compare to other tools.

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