ncloud_delete_acg

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

Annotations already mark it as destructive and idempotent. The description reinforces the destructive nature with a warning emoji and the confirm=true requirement, adding value beyond annotations. No contradiction detected.

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 warning emoji. Every word serves a purpose; no wasted content.

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 essential behavior and key parameter. No output schema exists, but return values are implicit. Minor gap: it does not mention that the operation is safe without confirm or any post-delete effects.

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 schema already describes all parameters with 100% coverage. The description adds emphasis on the confirm parameter ('Set confirm=true to execute'), but does not elaborate on vpcNo or accessControlGroupNo. 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 explicitly states 'Delete an Access Control Group', providing a clear verb and resource. It is distinct from sibling tools like remove_acg_inbound_rule and other delete operations.

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 highlights the confirm=true requirement to execute, which is crucial for safety. However, it does not provide guidance on when to use this tool versus alternatives (e.g., removing individual rules), or mention any prerequisites or consequences.

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