blender_save_checkpoint

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

The description adds meaningful behavioral context beyond the annotations: it never overwrites an existing file and verifies that saving did not change the live scene. These details are not already present in readOnlyHint, destructiveHint, or idempotentHint, and they do not contradict the annotations.

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?

Two dense sentences, with the core action first and the critical safety behaviors second. Every clause earns its place and there is no filler.

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 one-parameter tool, the essential behavior is covered: create, version, never overwrite, verify live scene. However, with no output schema and no usage guidance relative to the many snapshot-related siblings, the description leaves some selection and invocation ambiguity.

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 'path' as a non-empty string, and schema description coverage is 0%. The description says the deliverable is placed under CODEX3D_ARTIFACT_ROOT and is versioned, which gives some context, but it does not clarify whether 'path' is relative to that root, an absolute path, a file name, or how existing paths are handled.

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 action ('Create a new, versioned .blend delivery') and a clear location ('under CODEX3D_ARTIFACT_ROOT'), so the core purpose is unambiguous. It does not explicitly distinguish itself from the sibling blender_create_snapshot, though the artifact-root and versioned-delivery wording hints at a difference.

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?

There is no guidance about when to call this tool versus alternatives such as blender_create_snapshot, blender_list_snapshots, or blender_restore_snapshot. No exclusions, prerequisites, or decision criteria are provided, so the agent must infer usage from the name and description.

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