ncloud_delete_monitor_group

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

The description adds a destructive warning and states permanent removal, which aligns with the annotations (destructiveHint=true). However, it does not disclose additional behavioral traits such as the need for the 'confirm' parameter to be true, nor does it mention that the operation is idempotent per annotations. With annotations covering the main safety profile, the description adds minimal extra value.

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: a single sentence with a warning icon. Every word is purposeful (destructive nature, action, resource, permanence). No wasted words.

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?

The description is minimal and lacks context about the 'confirm' parameter, the difference from force delete, and any required preconditions. For a destructive operation with a confirmation requirement and sibling tools, more detail is needed to ensure safe and correct usage.

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%, so the schema already fully documents the two parameters. The description does not mention parameters or add any semantic value beyond the schema. Baseline score of 3 applies.

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 resource ('Cloud Insight monitoring target group') with a warning icon. It distinguishes the tool from read-only operations but does not differentiate from the sibling 'ncloud_delete_monitor_group_force', which is a related destructive tool.

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 vs alternatives like 'ncloud_delete_monitor_group_force' or other monitoring group management tools. Prerequisites or required states (e.g., no active monitors) are not mentioned.

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