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

The annotation destructiveHint=true already declares that this is a destructive operation. The description adds the ownership constraint, which is useful, but it does not disclose irreversibility, required permissions, or what happens after deletion.

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 wasted words. It is appropriately sized for a simple delete operation.

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 simple operation, destructive annotation, and lack of output schema, the description is minimally adequate. It leaves gaps around ID format and post-deletion behavior, but the core action and ownership constraint are present.

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?

There is one required parameter ('id') with 0% schema description coverage. The description implies the parameter identifies an owned image, but it does not state the expected ID format or how to obtain it.

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?

States a specific verb ('Delete') and resource ('image') with an ownership scope ('you own'). This clearly distinguishes it from sibling image tools such as images_get, images_update, and images_share.

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 phrase 'you own' establishes a prerequisite for use, implying the tool is for deleting only owned images. However, it does not name alternatives or describe when not to use it versus tools like images_update or images_share.

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