cloud_delete_image

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

With no annotations, the description carries the full burden. It mentions that system images cannot be deleted, which is a key constraint. However, it does not disclose whether deletion is irreversible, any required permissions, rate limits, or side effects. This lack of behavioral detail is a significant gap for a delete operation.

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 extremely concise with two front-loaded sentences and no wasted words. It could be slightly improved by adding a brief note on the parameter, but it remains effective and not verbose.

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?

Given the tool's simplicity (one parameter, output schema exists), the description covers the core purpose and a key constraint. However, it omits details about the output, error cases, and irretrievability of the action, making it adequate but not fully 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?

The description does not elaborate on the image_id parameter beyond naming the operation's target (snapshot/backup image). Since schema description coverage is 0%, the description should provide additional context, but it adds no meaning about parameter format, example values, or how to obtain the ID.

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 tool deletes a snapshot or backup image, and explicitly notes that system images cannot be deleted. This provides a specific verb+resource with a distinct constraint, effectively differentiating it from other delete tools and image-related tools.

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 specifies the tool is for deleting snapshots or backup images, but does not provide explicit when-not-to-use guidance or name alternative sibling tools. While it implies system images are not eligible, it fails to direct the user to an alternative, such as update_image, leaving some ambiguity.

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