penpot_checkpoint

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

Despite no annotations, the description fully discloses behavioral traits: snapshot scope, persistence (disk vs memory based on server config), reusability, and lifecycle. It also explains the relationship with other checkpoint tools.

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 well-structured paragraph that front-loads the core purpose and progressively adds detail. It is concise without unnecessary words, though bullet points could improve scanability.

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 tool with 2 parameters and no output schema, the description comprehensively covers input semantics, side effects, persistence behavior, and lifecycle. It provides all necessary context for an agent to invoke correctly.

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?

With 0% schema description coverage, the description adds significant meaning: clarifies that pageId scopes snapshot to a single page and omitting it creates a whole-file checkpoint. fileId is implied but not elaborated, but the schema already marks it required.

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: 'Snapshot shapes so a subsequent penpot_restore_checkpoint call can undo whatever happens between now and then' and gives a concrete scenario (undo delete_shapes). It distinguishes itself from sibling tools like penpot_restore_checkpoint and penpot_discard_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?

Explicit guidance on when to use ('Call this immediately before a risky multi-step edit'), how to supply pageId vs omit it for whole-file checkpoint, and what to do with the returned checkpointId. The description also clarifies reuse and discard lifecycle.

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