pbs_snapshot_delete

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

With no annotations, the description carries full burden and clearly states the mutation is destructive ('permanent — no undo'), dry-run by default, and synchronous. This gives sufficient behavioral insight.

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 a single, efficient sentence that immediately conveys the purpose and key behavioral traits (mutation, dry-run, permanence, sync). 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?

The description covers major behavioral aspects (dry-run, permanence, sync) and acknowledges the output schema exists. However, it omits prerequisites (e.g., snapshot not protected) and error conditions, which are important for a 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 only 14% (only proximo_target has a description). The description adds meaning only for the confirm parameter ('confirm=True to execute'), leaving the four required identification parameters (store, backup_type, backup_id, backup_time) unexplained, which could lead to incorrect invocation.

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 ('delete') and the resource ('specific backup snapshot / recovery point'), and distinguishes it from sibling tools like pbs_snapshots_list, pbs_snapshot_notes_set, and pbs_snapshot_protected_set.

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 provides clear guidance on when to use the tool (delete a snapshot) and how to use it safely (dry-run by default, confirm=True to execute). It highlights the permanent nature but does not explicitly mention alternatives like pbs_prune for bulk cleanup.

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