ncloud_delete_member_server_images

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

The description adds the confirm gate and explicitly warns 'Destructive', which goes beyond the destructiveHint annotation by explaining the execution requirement. It does not contradict the idempotentHint annotation and reinforces the destructive nature clearly.

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, concise sentence with the warning and key instruction front-loaded. Every word earns its place, making it highly efficient and scannable.

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 delete operation with a confirm flag, the description covers the essential context: destructive potential, execution requirement, and target resource. It lacks details on return values or side effects, but given the absence of an output schema and the straightforward nature, the description is sufficiently complete.

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 input schema already provides descriptions for both parameters (confirm and memberServerImageInstanceNoList), covering 100% of the parameters. The description's mention of 'Set confirm=true' mirrors the schema's confirm description without adding new semantic value.

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 a specific action ('Delete') on a specific resource ('member server image instances'), including the batch nature ('one or more'). This distinguishes it from similar sibling tools like ncloud_delete_server_images, which targets a different resource type.

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 provides critical usage guidance by stating that confirm=true is required to execute the destructive operation. This is an explicit operational prerequisite. However, it does not explicitly discuss when to use this tool versus alternatives beyond the resource type.

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