ncloud_delete_cache_config_group

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

Annotations already flag destructiveHint, but the description adds valuable context: 'Permanently' highlights irreversibility, and 'Set confirm=true to execute' reveals the safety mechanism that prevents accidental deletion without explicit confirmation. 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?

A single, front-loaded sentence with a clear warning symbol. Every word is purposeful: 'Destructive' warns, 'Permanently' stresses irreversibility, and the confirm requirement is concise. No filler or redundancy.

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 destructive delete tool with two well-documented parameters, the description adequately covers purpose, permanence, and the confirmation gate. It could mention dependencies (e.g., whether the config group must be unused) or return values, but the annotations and schema fill most gaps, making it sufficiently complete for safe invocation.

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 100% coverage with descriptions for both parameters (cloudCacheConfigGroupNo and confirm). The description's mention of 'confirm=true' mirrors schema content without adding new parameter insights, so the baseline of 3 applies.

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 specific resource ('Cloud Cache config group'). The word 'Permanently' adds precision about irreversibility, making the tool's purpose unambiguous and easily distinguishable from sibling operations.

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 gives an operational instruction ('Set confirm=true to execute') but no explicit comparison to alternative tools or conditions for when to use this delete operation. Usage is implied by the 'delete' verb, but without exclusion criteria or references to list/create counterparts.

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