pbs_snapshot_delete

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

Discloses mutation with HIGH impact, permanent deletion with no undo, dry-run behavior, synchronous execution, and the requirement for explicit confirmation. This adds value beyond the absence of annotations.

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 with no wasted words. Critical information is front-loaded, and structure is clear.

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 purpose, behavior, usage guidelines, and alternatives. With an output schema present, no further return-value explanation is needed. Complete for a deletion tool.

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?

All 7 parameters are described in the schema (100% coverage), so the description adds minimal parameter-level detail beyond mentioning confirm=True. Baseline 3 is appropriate.

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 a specific backup snapshot from a PBS datastore') and differentiates from sibling tools by mentioning alternatives like pbs_snapshot_protected_set and pbs_prune.

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 states when to use (to delete a snapshot), the dry-run default, the need for confirm=True, and gives specific alternatives for protecting or bulk deletion.

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