save_manage

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

No annotations are present, so the description carries the full burden. It meaningfully discloses behavioral details: atomic and corruption-resistant writes, automatic orchestration across nodes in the 'saveable' group, optional encryption, and slot metadata listing. It does not go into error or auth behavior, but the core side effects of each op are stated.

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 a compact, scannable list of operations with signatures and one-line semantics, followed by the canonical call shape. Every line adds necessary information and there is no filler or 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?

Given the tool has multiple internal operations and an output schema, the description is sufficient: it defines call shape, op names, params, defaults, and behavioral guarantees. It also covers the compatibility alias for flat parameters, so an agent has what it needs to invoke any listed op.

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 input schema only defines op/params/session_id with 0% description coverage, but the description provides full per-op signatures with defaults and explanations (e.g., save_slot(slot_name='slot_1', data={}, directory='user://saves/')). It fully compensates for the schema's lack of param detail.

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 opens with 'Save Game and Persistence Management' and then enumerates five specific operations (scaffold_save_system, save_slot, load_slot, list_slots, delete_slot), each with a clear verb and target resource. This makes it easy to distinguish from sibling management tools like scene_save or filesystem_manage.

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 title and op list provide clear context: use this tool for save/load slot orchestration, scaffolding a SaveManager, listing slots, and deleting saves. It does not explicitly name alternatives or state when-not-to-use, but the operation names and descriptions make the appropriate usage obvious.

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