create_snapshot

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

No annotations are provided, so the description carries full burden. It discloses that snapshots are stored outside the vault, with date and reason ('Se guarda fuera de la bóveda, con fecha y motivo'). This is transparent for a backup creation tool, though it could clarify if it overwrites existing snapshots.

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 concise sentences, front-loaded with the main purpose. No unnecessary information; every sentence adds value.

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 tool with one optional parameter and no output schema, the description covers the functionality, behavior, usage context, and relation to siblings. It is complete and sufficient for an AI agent to understand and invoke the tool 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?

Schema description coverage is 100% (reason parameter documented). The description adds context by stating that the reason is used 'para reconocerla luego' (to recognize it later), supplementing the schema's 'Motivo, para reconocerla luego (ej. ...)'.

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: creating a complete backup ('copia de seguridad completa') of the vault, especially before risky actions. It distinguishes itself from siblings like 'restore_snapshot' and 'list_snapshots'.

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 advises using this tool 'antes de hacer algo arriesgado' (before doing something risky) and mentions the corresponding restore tool ('restore_snapshot') for returning to the snapshot. This provides clear when-to-use and alternatives.

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