rbd_snapshot_delete

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

No annotations are provided, so the description carries full burden. It explicitly labels the tool as '[WRITE][risk=high]' and states 'Irreversible.' It also reveals the approval requirement, offering comprehensive transparency about the tool's destructive nature and prerequisites.

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 concise and well-structured: a header line with risk and action, followed by essential notes on dry_run and approval, then a compact Args list. Every sentence serves a purpose without redundancy.

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 destructive nature and five parameters, the description covers all critical aspects: operation type, risk, irreversibility, preview option, authorization requirement, and parameter explanations. No output schema is needed as the action only deletes with no meaningful return value.

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?

With 0% schema description coverage, the description compensates by listing all five parameters in the Args section and providing brief, clear explanations (e.g., 'dry_run: If True, preview without deleting'). While types are already in the schema, the descriptions add meaningful context for correct usage.

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 'Delete an RBD image snapshot. Irreversible.' The verb and resource are explicit. While it doesn't explicitly differentiate from siblings like rbd_snapshot_create or rbd_image_delete, the purpose is unmistakable and specific to snapshot deletion.

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 advises using 'dry_run=True to preview' and notes that it 'Requires an approver (CEPH_AUDIT_APPROVED_BY).' These guidelines provide crucial context for safe usage, though it does not explicitly mention when not to use it or list alternative tools.

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