delete_image

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

Annotations provide no safety hints, so the description carries the full burden of disclosing that this is a destructive operation. It does not mention irreversibility, whether deletion affects only the in-memory session, or any side effects. For a delete tool, this is a significant transparency gap.

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 a single, front-loaded sentence with no filler. It efficiently communicates the action and scope, which is appropriately concise for a single-parameter tool.

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?

Even though the tool is simple and has an output schema, the description omits important behavioral context for a destructive operation: undoability, persistence, and error behavior. The sibling tools include undo and get_undo_count, so the interaction between deletion and undo is a relevant detail that is not addressed.

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 coverage is 100%, and the only parameter, image_id, is already documented as 'ID of the image to delete'. The description adds no extra semantic detail, such as where to obtain the ID or session-specific scoping nuances, so the baseline of 3 applies.

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 clear action ('Delete') on a specific resource ('an image') and scopes it to the session, which distinguishes it from sibling image tools like list_images, get_image, or duplicate_image. There is no ambiguity about what the tool does.

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?

No guidance is provided on when to use delete_image versus alternatives such as undo or save_image. The description is purely declarative and does not mention prerequisites, exclusions, or decision criteria for choosing this tool.

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