ncloud_delete_acg

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

The description adds the critical behavioral detail that confirm=true is required to execute, which is not covered by the destructiveHint annotation. This explains the safety mechanism. The idempotentHint annotation is not elaborated, but the confirmation requirement is valuable 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?

One concise sentence with a clear warning prefix. Every word serves a purpose, front-loading the destructive nature and immediately indicating 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 straightforward delete operation, the description covers the essential behavior: destructive, requires confirmation, and identifies the resource. The annotations provide safety hints. It lacks details about dependencies or errors, but these are not critical for a simple ACG deletion.

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%, providing baseline meaning for all parameters. The description adds specific instruction that confirm must be true to execute, enriching the semantic understanding of the confirm parameter beyond its schema description.

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 'Delete an Access Control Group' with a specific verb and resource, distinguishing it from sibling operations like ncloud_delete_vpc or ncloud_delete_subnet. The destructive warning immediately identifies the action's nature.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., VPC existence, ACG not in use) or scenarios where deletion is appropriate. The confirm flag is mentioned but not as a usage guideline.

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