Delete system backup

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

No annotations exist, so the description carries the full burden of behavioral disclosure. It explicitly labels the operation 'Destructive' and forbids unsanctioned use, which clearly communicates the risk profile. It stops short of describing exactly what is affected or whether the deletion is reversible, but it covers the critical safety behavior.

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 sentences, all substantive: purpose, destructive warning, and documentation link. No filler or repetition of schema details. The most important safety information is front-loaded immediately after the purpose statement.

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 one-parameter destructive delete operation, the description includes the essential safety warning and a documentation link. It is mostly complete, but it could be slightly stronger by noting that the deletion is permanent and that valid backup names can be found via systembackup_list. These are minor gaps for such a simple 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?

The schema has a single 'name' parameter with no description, and the description does not explicitly state that 'name' refers to the system backup's identifier or how to obtain valid names. The meaning is inferable from context, but the description adds little beyond what the parameter name already implies.

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 states a specific verb and resource: 'Delete a Longhorn system backup.' This clearly distinguishes it from sibling tools like systembackup_list, systembackup_get, and systembackup_create. The purpose is unambiguous and immediately actionable.

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 explicit when-not guidance: do not call unless the user has explicitly authorized it, and never proactively, speculatively, or as a side effect. It does not name alternatives, but for a destructive operation the authorization constraint is the most important routing information.

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