ncloud_delete_server_images

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

The description explicitly marks the tool as 'Destructive' and requires 'confirm=true', adding behavioral context beyond the annotations (destructiveHint: true, idempotentHint: true). No contradiction with annotations.

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?

Extremely concise: one sentence with a warning emoji. The most critical information (destructive nature and confirm requirement) is front-loaded. No unnecessary words.

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?

The description covers the action and safety requirement, but it does not describe the return value or error scenarios. For a destructive tool without an output schema, more detail on expected response or side effects would be beneficial.

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 already provides descriptions for both parameters (100% coverage). The description adds value by explaining that 'confirm' must be true to execute, going beyond the schema. No additional info for serverImageInstanceNoList, but sufficient.

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 action 'Delete' and the resource 'server image instances', with a warning emoji indicating destructiveness. The purpose is unambiguous and distinguishes it from sibling tools like ncloud_get_server_images or ncloud_create_server_image.

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 provides a clear usage guideline: 'Set confirm=true to execute'. However, it does not explicitly state when to use this tool versus alternatives like ncloud_delete_member_server_images, but the resource is sufficiently distinct.

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