blender_restore_snapshot

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

The description discloses key behaviors beyond the annotations (all false): it creates a non-overwriting pre-restore safety snapshot and returns an inspection and scene diff. This adds valuable context about side effects and output. It does not contradict the annotations, and while it omits potential failure modes, it covers the main behavioral aspects adequately.

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 single, compact sentence that leads with the core purpose and then adds necessary operational details. There is no redundancy or filler, and the structure is clear and front-loaded.

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 complex mutation tool with no output schema and no useful annotations, the description provides a good overview but leaves gaps: it does not describe the exact structure of the 'inspection' or 'scene diff', does not explain error conditions (e.g., fingerprint mismatch), and does not specify the return format. These are important for an agent to call it correctly without additional inference.

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 no parameter descriptions (0% coverage), so the description must explain all parameters. It clarifies that current_fingerprint and snapshot_fingerprint are the 'live' and 'target' fingerprints, but it does not explain snapshot_id, its purpose, or its relationship to the fingerprints. This partial explanation does not fully compensate for the lack of schema documentation.

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 the tool's purpose: it restores a snapshot registered by the current session, and explicitly notes it is reversible and creates a safety snapshot. This is a specific verb+resource and distinguishes it from sibling tools like blender_create_snapshot, blender_list_snapshots, and blender_delete_snapshot.

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 description gives a condition ('Requires the live and target fingerprints') but provides no guidance on when to choose this tool over alternatives. It does not mention scenarios where a different snapshot operation (e.g., create, delete) would be more appropriate, nor does it state prerequisites like the snapshot must be from the current session beyond the phrase 'registered by the current session'.

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