ncloud_resource_detach_group

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

The description adds the behavioral nuance that the operation is destructive and requires a confirmation flag (confirm=true) to actually execute, which is not fully captured by the destructiveHint annotation alone. It also clarifies that the effect is removing resources from a group, not deleting them. This is valuable context beyond the 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?

The description is a single, front-loaded sentence with a clear warning symbol and the essential instruction. Every word contributes to understanding the tool's purpose and the critical confirm requirement, with no wasted text.

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 destructive operation with three parameters and no output schema, the description covers the core action, the confirmation requirement, and the destructive nature. It lacks details about return values or potential side effects, but given the tool's simplicity and the annotations covering idempotency/destructiveness, it is sufficiently complete for an agent to invoke 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?

The input schema already provides full descriptions for all three parameters (confirm, groupId, nrnList) with 100% coverage. The description's mention of 'Set confirm=true' reinforces the confirm parameter's purpose but doesn't add new meaning beyond the schema's existing description. Therefore, a baseline score of 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 uses the specific verb 'Remove' and clearly identifies the resource being acted upon: 'resources from a resource group.' This distinguishes it from sibling tools like ncloud_resource_attach_group and ncloud_resource_detach_tag, which involve adding to a group or removing tags.

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 implicitly tells when to use: when you need to detach resources from a group. It provides a critical usage guideline with 'Set confirm=true to execute,' indicating the required confirmation step. However, it doesn't explicitly name alternatives or state when not to use this tool, but the context is clear.

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