ncloud_delete_member_server_images

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds a warning emoji and repeats 'Destructive', which is redundant. It does add the confirm requirement, which is useful extra behavioral context beyond 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?

Two short sentences that are front-loaded with the warning and purpose. Every word earns its place; no filler.

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 tool, the description covers the core action and safety requirement. Annotations handle destructive and idempotent hints. No output schema exists, but return values are typically simple status messages. Minor improvement could be mentioning idempotency (but annotation covers it).

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 coverage is 100%, so baseline is 3. The description does not elaborate on parameters beyond what the schema already provides (e.g., the schema already describes confirm and memberServerImageInstanceNoList). No additional semantic value is added.

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 explicitly states 'Delete one or more member server image instances', clearly identifying the verb (delete) and resource (member server image instances). The warning emoji and 'Destructive' further clarify the action. It distinguishes from siblings like ncloud_delete_server_images by specifying 'member server'.

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 one key guideline: 'Set confirm=true to execute', which informs agents that the operation requires explicit confirmation. However, it lacks guidance on when to use this tool vs. alternatives (e.g., ncloud_delete_server_images) or any prerequisites (e.g., image must not be in use).

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