Delete backup backing image

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

With no annotations, the description carries the full burden of behavioral disclosure, and it does so well: it explicitly labels the operation 'Destructive,' states that deletion happens from the backup target, and imposes a strict authorization prerequisite. This tells the agent what is at risk and under what conditions the call is acceptable.

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 compact and front-loaded: the action comes first, then the critical destructive/authorization warning, then a reference link. Every sentence earns its place and there is no redundancy with the schema or title.

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 operation with no output schema, the description is largely complete: it identifies the target, the destructive nature, and the authorization guardrail, and provides documentation. It does not explain how to discover valid names or what a successful call returns, but those are minor given the operation's simplicity.

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 input schema only defines required string `name` with 0% coverage, and the description does not explain the parameter's format or source. However, the context 'Delete a backup backing image' makes it reasonably inferable that `name` identifies which backup backing image to delete, and the single simple parameter limits ambiguity.

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 action and resource: 'Delete a backup backing image from the backup target.' This clearly distinguishes it from related tools such as backingimage_delete by specifying the backup-target scope, so an agent can tell what is being operated on without inspecting the schema.

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 condition: it must only be called when the user has explicitly authorized it, never proactively or as a side effect. This is strong operational guidance for a destructive tool, but it does not point to alternative tools for discovery or restoration, such as backupbackingimage_list or backupbackingimage_get.

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