ksp_game_load_save

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

No annotations are provided, so the description carries full burden. It leaves the mutation semantics vague: does it overwrite current game state, require KSP to be running, block until loaded, or fail if already in a scene? For a load/mutation tool with zero annotation coverage this is a significant gap.

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?

One sentence, front-loaded with the action, with no filler. It is tight, though the phrase 'avoiding title-screen Computer Use' is slightly cryptic jargon for an external agent.

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?

For a stateful game-loading tool with no annotations, no output schema, and undocumented parameters, the description omits prerequisites (KSP running), blocking behavior, failure modes, and return value. The sibling tool names suggest a coordinated workflow that this description does not acknowledge.

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?

Schema description coverage is 0% for the single required parameter save_folder. The description mentions 'save' but gives no format, whether it is a folder name vs path, or where saves live; the agent must guess. A brief example (e.g. 'folder name under KSP/saves') would have closed the gap.

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?

States a specific verb+resource: load a KSP save via GamePersistence and enter the Space Center scene. Clearly distinguishable from ksp_editor_load (craft loading) and ksp_game_list_saves (enumeration), and the 'real' qualifier plus the save-folder param disambiguate it from listing tools.

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 trailing clause 'avoiding title-screen Computer Use' hints at when this is preferred over manual UI navigation, but it never states preconditions, what happens if the game is already in-flight, or which alternatives (e.g. ksp_wait_for_scene, ksp_game_list_saves) pair with it.

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