create_checkpoint

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

With no annotations, the description carries the behavioral burden. It discloses atomicity and scope, which is useful, but it does not mention effects on existing checkpoints, retention limits, or whether a checkpoint identifier is returned for later rollback.

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, well-structured sentence with no filler. The core behavior is front-loaded and every word earns its place.

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?

The tool is simple, has full schema coverage, and the description conveys the essential purpose and rollback relationship. It does not explain the return value or checkpoint lifecycle, but those are secondary for a low-complexity creation operation.

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 100%, so the schema already documents all three parameters. The description adds context about 'current artboards or nodes' but does not meaningfully extend parameter understanding beyond the schema.

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 uses a specific verb ('Saves') and a specific resource ('atomic snapshot checkpoint of current artboards or nodes'). It clearly distinguishes this creation action from related siblings like list_checkpoints and rollback_checkpoint.

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 phrase 'for 1-click rollback' implies this should be used before making changes that might need to be reverted, but there is no explicit when-to-use guidance or mention of alternatives. The tool's relationship to undo_last_transaction or apply_document_transaction is not addressed.

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