ncloud_delete_rule_group

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

Annotations already flag destructiveHint and idempotentHint, and the description adds context beyond those: it specifies that deletion is permanent and that associated monitoring alerts are stopped. This gives the agent a concrete understanding of consequences without contradicting 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 extremely concise: two sentences, with the critical warning front-loaded. Every word contributes value, and no unnecessary details are included.

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 destructive delete operation with only two parameters and no output schema, the description provides essential context: the warning, the permanence, and the impact on monitoring alerts. Combined with the annotations and schema (which cover the confirm behavior), the tool is fully understood for correct invocation.

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 fully documents both parameters with clear descriptions (confirm and ruleGroupId), and the schema coverage is 100%. The tool description does not add parameter-specific meaning beyond what the schema provides, so the baseline 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 clearly states the action: 'Delete a Cloud Insight event rule group.' It specifies both the verb and the resource, distinguishing it from related tools like ncloud_update_rule_group or ncloud_copy_rule_group. The additional consequence 'stop all associated monitoring alerts' further clarifies the scope and impact.

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 emphasizes the destructive nature with a warning, and the schema's confirm parameter implies a safety guideline, but it does not explicitly state when to use this tool versus alternatives like ncloud_delete_rule_group_by_id. No clear exclusions or alternative-selection guidance is provided, leaving some ambiguity.

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