ncloud_cdss_delete_config_group

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds crucial context: a confirm=true guard is required to execute, and the destructive effect is flagged with a warning emoji. This exceeds the baseline by explaining the safety mechanism beyond what annotations provide.

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 one compact sentence with a warning, a prerequisite, and the execution condition. Every word earns its place; the destructive warning is front-loaded, and the instruction to check clusters comes before the execution requirement.

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 2 parameters and no output schema, the description covers the essential prerequisites and guard. The only minor gap is not describing the return value or post-delete state, but the annotations and schema cover most of what an agent needs.

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 parameters are documented. The description reinforces that confirm must be true to execute, which is the most important semantic. It doesn't add extra detail about configGroupNo, but the schema already covers it. Slight deduction because no additional contextual meaning beyond schema is provided, but the critical confirmation flag is highlighted.

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 ('Delete') and resource ('Config Group') with clear scope. It also distinguishes itself from sibling tools like ncloud_cdss_create_config_group and ncloud_cdss_apply_config_group by the destructive action and explicit pre-check instruction.

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 explicitly instructs the agent to check which clusters still use the config group via ncloud_cdss_get_config_group_clusters before deleting. This is a clear when-to-use and prerequisite step that differentiates safe usage from dangerous usage.

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