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

With no annotations, the description carries the behavioral disclosure burden. It states the deletion scope (one image per token, uploaded or generated) and the refusal behavior for unknown names, including that nothing is deleted. It does not explicitly say deletion is permanent or irreversible, but 'delete' strongly implies it and the token scoping is useful context.

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 short sentences with no filler. The core action is front-loaded, followed by the name semantics, a list source, and the invalid-name edge case. Every sentence earns its place.

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 one-parameter destructive tool with no output schema, the description covers the action, scope, how to discover valid inputs, and error behavior. Nothing essential is missing for an agent to call it correctly.

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 0% description coverage, so the description must compensate. It does this well by explaining that name is the stored name, and by directing the user to image_files to find valid names. This adds meaning far beyond the raw string type and length constraints in the schema.

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 a specific verb and resource: 'Delete one image stored for your token, uploaded or generated'. It clearly distinguishes the tool from siblings like image_upload and image_files by stating its destructive action and the exact object it operates on.

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?

It gives clear context for when to use the tool and points to image_files as the way to discover valid names. It does not explicitly name alternatives, but no other sibling performs deletion, so no exclusion is necessary. The invalid-name refusal behavior also sets expectations for misuse.

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