Delete VolumeSnapshot CR

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

With no annotations, the description itself carries the burden of disclosing behavior. It explicitly warns 'Destructive' and mandates explicit user authorization, which covers what gets destroyed and the auth requirement. It does not mention irreversibility or downstream effects on backups, but the core destructive nature is clearly flagged.

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 short, front-loaded with the action, and every sentence earns its place: the purpose, the destructive warning, the authorization guardrail, and a doc link. No filler.

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 delete tool, it covers the purpose and safety, but the complete absence of parameter semantics is a significant gap. An agent cannot reliably construct a correct invocation because it doesn't know what values these two required fields should take.

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 0%, so the description was the only place to explain the parameters, and it does not. Neither 'name' nor 'snapshotName' is defined or given context, leaving the agent to guess which refers to the volume and which to the snapshot.

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 uses the specific verb 'Delete' and identifies the exact resource: a CRD-backed snapshot for a volume. The 'CRD-backed' qualifier distinguishes it from the sibling volume_snapshot_delete, so an agent can tell them apart.

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 gives an explicit when-not: do not call unless the user has explicitly authorized it in this conversation, never proactively, speculatively, or as a side effect of another task. It does not, however, point to an alternative tool for non-CRD snapshots, so it stops short of full alternative routing.

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