penpot_restore_file_snapshot

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

With no annotations, description carries full burden. It discloses that restore replaces live data, affects all agents and browser sessions, and that an automatic backup snapshot is created. This gives full transparency about side effects and recoverability.

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?

Three sentences: first states core action, second explains safety undo mechanism, third lists prerequisites. No filler, front-loaded with purpose, each sentence adds essential information.

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?

No output schema, but description does not mention return value or success/failure indicators. However, for a mutation tool with clear side effects and undo capability, it covers the key aspects except output. Slightly incomplete.

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 0%, so description must add meaning. It explains that fileId and snapshotId come from penpot_list_file_snapshots, but does not elaborate on their format or constraints beyond the schema's minLength. Provides context but limited parameter-specific detail.

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 restores a file to a snapshot state, using verb 'Restore' and specifying the resource (file via snapshot). It distinguishes from siblings like penpot_create_file_snapshot and penpot_get_file_snapshot by referencing the UI equivalent and linking to penpot_list_file_snapshots for obtaining IDs.

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?

Explicitly states prerequisites: requires fileId and snapshotId from penpot_list_file_snapshots. Also notes that a system backup snapshot is created automatically, allowing undo. Does not specify when not to use, but purpose is clear.

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