ncloud_delete_deny_allow_group

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

The description goes beyond annotations by specifying the confirm safeguard and emphasizing permanence ('permanently delete'). Annotations already indicate destructiveHint and idempotentHint, but the description adds practical execution requirements.

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 extremely concise, using a single sentence with a clear emoji warning and actionable instruction. Every word serves a purpose with no redundancy.

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 with no output schema, the description adequately covers the destructive nature and confirmation requirement. It could mention the operation's effect on associated resources but is sufficient for an agent to understand the core action.

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 description coverage is 100% with clear parameter descriptions. The description only reiterates the confirm requirement, adding no new semantic value beyond what the schema provides, meeting baseline expectations.

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) and the specific resource (Network ACL Deny-Allow Group). It uses a strong verb and distinguishes from sibling tools like ncloud_delete_network_acl and ncloud_delete_cache_config_group by targeting a unique resource.

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 explicit usage guidance with 'Set confirm=true to execute' and warns about destructiveness. While it doesn't explicitly list alternatives or when-not-to-use, the resource-specific nature makes the use case unambiguous.

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