penpot_rename_file_snapshot

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

Lacking annotations, the description carries full burden. It discloses the critical constraint (user-created only) but omits other behavioral details like return value, confirmation of success, or idempotency. Adequate for a simple rename operation.

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 sentences, no redundant information. The action and constraint are front-loaded, achieving maximum clarity with minimal words.

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 simple rename tool with two required parameters and no output schema, the description covers the essential constraint. Minor gap: could mention that 'label' is the new name, but schema names imply it.

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%, yet description adds no parameter details beyond the names 'snapshotId' and 'label'. It does not explain the label is the new name or any constraints like max length or uniqueness. Fails to compensate for missing schema descriptions.

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 action ('Rename') and resource ('existing user-created snapshot'), and distinguishes from sibling tools like penpot_create_file_snapshot and penpot_lock_file_snapshot by specifying the constraint that only user-created snapshots can be renamed.

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?

Description explicitly states when to use (only for snapshots with createdBy 'user') and when not to (system-created automatic backups will error), providing clear usage boundaries. No alternative tools mentioned, but the constraint is sufficient.

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