ncloud_delete_group

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description adds critical behaviors: the deletion is permanent and requires confirm=true to execute. This explains the safety mechanism and warns of irreversibility. It does not contradict the annotations and provides extra context.

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 that includes a warning emoji, the action, and the critical confirm gate. Every word earns its place, and it is front-loaded with the destructive warning, making it highly efficient.

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 with two parameters and no output schema, the description covers the essential information: the action is destructive, permanent, and requires confirmation. It does not describe prerequisites (e.g., whether the group must be empty) or return values, but given the low complexity and the annotations, the description is sufficiently complete for an agent to use it safely.

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 100% of parameters with descriptions (groupId and confirm). The description reinforces the confirm parameter's purpose ('Set confirm=true to execute') but does not add new semantics beyond what the schema already states. Thus 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 tool's function: 'Permanently delete an IAM group.' The verb 'delete' with the specific resource 'IAM group' distinguishes it from sibling tools like ncloud_create_group or ncloud_attach_policy_to_group. It also includes the critical confirm requirement, making the purpose unambiguous.

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 context for when to use the tool (to permanently delete an IAM group) and explicitly states the prerequisite of setting confirm=true to execute. It does not mention alternatives or exclusions, but the resource type is clearly named, so an agent can infer when this tool is appropriate.

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