ncloud_ncr_delete_image

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful context beyond the annotations: the deletion is permanent, the resource is a container image in a registry, and confirm=true is required to execute. It does not mention auth or rate-limit behavior, but it adds meaningful destructive-operation 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?

The warning is front-loaded, the action is stated immediately, and the endpoint plus confirm requirement are included without wasted words. It is appropriately sized for a destructive single-resource delete 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?

With no output schema, the description does not need to explain return values, and the input schema plus annotations cover parameters and safety. The description supplies the destructive warning, permanence, endpoint, and confirm gate, though it could include alternative-tool guidance for a fully complete selection context.

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 description coverage is 100%, so registryName, imageName, and confirm are already documented in the schema. The description adds the DELETE path template showing registryName and imageName placement, but otherwise mainly repeats the confirm=true requirement, matching the baseline for high schema coverage.

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 verb and resource: deleting a container image from a registry, with the exact HTTP endpoint shape. It distinguishes the tool from sibling operations such as delete_registry and delete_tag by naming the image as the deleted resource.

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 implies usage through the destructive delete action and gives the confirm=true execution prerequisite. However, it does not explicitly say when to choose this over ncloud_ncr_delete_tag, ncloud_ncr_delete_registry, or list/get tools, nor does it state exclusions.

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