checkpoint

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

With no annotations, the description carries the full burden, and it does usefully disclose that restore replaces the current scene's objects with the snapshot and that the user's .blend file is untouched — an important non-destructive guarantee. But it is silent on the destroy/mutation semantics of delete, whether snapshots persist across sessions, and idempotency, leaving notable gaps for a 4-action tool.

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?

A single front-loaded sentence with a useful parenthetical clarification; no filler or redundancy. It is efficient, though the brevity is partly why the other actions go unexplained.

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 mutation tool with no annotations, no output schema and 0% parameter coverage, the description covers the destructive/rollback concept and the .blend safety guarantee but leaves the list and delete actions, the name parameter, and persistence behavior unexplained. Adequate but with clear gaps.

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%, so the description must compensate. It implies the save and restore actions and mentions 'roll back' but never explains the 'name' parameter, nor what list and delete do or how they interact with name. Two of the four enum values are entirely undocumented anywhere.

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 states a specific verb+resource (snapshot the scene / roll back) and frames it around a clear scenario ('before risky edits'), which is distinguishable from siblings like clear_scene or get_scene_info. It stops short of explicitly naming alternative tools or how it relates to them, but the core purpose is unambiguous.

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?

It gives a clear when-to-use for the save/restore workflow ('before risky edits... roll back if they go wrong'), which is helpful implied usage. However, the schema's four actions (save, restore, list, delete) are never differentiated in the description, so an agent gets no guidance on when to pick list or delete versus save/restore.

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