rollback_snapshot

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

WARNING explicitly states 'destroys newer data', a critical behavioral trait. Without any annotations, the description clearly discloses destructive behavior and the confirm requirement.

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 concise sentences, each adding value: purpose, requirement, warning. No unnecessary 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?

Covers core purpose and key behavioral aspects. Lacks explicit mention of prerequisite (snapshot existence) but output schema likely covers return values. Adequate for a simple destructive operation.

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 is 0%, so description carries burden. It clarifies that confirm must be true, adding meaning beyond the default false in schema. Snapshot_name is not elaborated, but the usage is straightforward.

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 'Rollback dataset to snapshot', using specific verb and resource. It distinguishes from sibling tools like create_snapshot, delete_snapshot, or clone_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?

Explicitly requires 'confirm=True' and warns about destroying newer data, which implies when to use. However, it does not explicitly compare to alternatives or state when not to use.

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