ncloud_cdss_delete_config_group

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

The annotations already mark destructiveHint and idempotentHint. The description adds the confirmation gate requirement, which is a meaningful behavioral detail not present in annotations or schema alone.

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 short sentence with a front-loaded warning, conveying all essential information without 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?

For a simple delete operation, the description covers the core action, the destructive nature, and the confirmation requirement. It lacks details about post-deletion behavior or prerequisites, but these are not critical given the simple scope and annotations.

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 covers both parameters with concise descriptions, so the description adds little beyond reinforcing the confirm flag. With 100% schema coverage, baseline 3 is appropriate.

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 a Config Group', with an explicit destructive warning. It distinguishes this tool from siblings that list, create, or apply config groups by its specific delete operation.

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 the execution requirement 'Set confirm=true to execute', but does not explicitly state when to use this tool versus alternatives or any prerequisites. Usage is implied by the resource type and action.

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