penpot_delete_file_snapshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that system-created backups cannot be deleted, locked snapshots require prior unlocking, and only user-created snapshots are deletable. It does not mention whether deletion is irreversible or what response to expect, but the core behavioral constraints are well covered.

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 two sentences long. The first sentence clearly states the purpose, and the second adds vital constraints. Every sentence earns its place, and the information is front-loaded with no extraneous content.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides sufficient context for the core operation and constraints. However, it could be more complete by mentioning what happens after deletion (e.g., success response) or that the snapshotId must belong to a file, but these are minor omissions for a basic delete tool.

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 coverage for the single parameter is 0% (no descriptions in schema). The description does not add any meaning to snapshotId beyond what the schema provides (a required string). It fails to explain the format, source, or how to obtain the snapshotId, leaving the agent without guidance on constructing the argument.

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: 'Delete a user-created snapshot.' It specifies the condition for deletable snapshots (createdBy: 'user') and distinguishes from system backups, which cannot be manually deleted. This differentiates it from sibling tools like penpot_create_file_snapshot, penpot_restore_file_snapshot, and penpot_lock_file_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 explicitly states when to use this tool (only for user-created snapshots) and when not to (locked snapshots or system backups). It also provides an explicit alternative: if a snapshot is locked, call penpot_unlock_file_snapshot first. This gives clear usage guidance.

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