ncloud_delete_rule_group_by_id

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

The description repeats the `destructiveHint` annotation with a warning emoji but provides no additional behavioral context. It does not disclose the confirmation requirement, idempotency details, side effects, or consequences beyond 'delete'. With annotations already providing the destructive hint, this adds no new transparency.

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 one concise sentence with a clear warning prefix. Every word is purposeful, no filler, and the structure front-loads the destructive warning.

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?

Despite being minimal, the tool is simple and the schema/annotations cover the critical confirm flag and destructive/idempotent hints. The description is complete enough for an agent to understand the core operation, although it omits explicit mention of confirm=true, which is still available in the schema.

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?

All parameters are documented in the schema (100% coverage), and the description does not add any parameter-specific meaning. The phrase 'by product key and rule group ID' maps to the existing schema fields but adds no details beyond the schema descriptions.

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?

States the exact operation: 'Delete a Cloud Insight event rule by product key and rule group ID.' This is a specific verb (Delete) and resource (Cloud Insight event rule) with the method of identification (product key and rule group ID), which distinguishes it from generic `delete_rule_group` and other rule-group related siblings.

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 like `ncloud_delete_rule_group` or `ncloud_delete_metrics_group_by_id`. The description only restates the operation and does not mention prerequisites, exclusions, or alternative tool choices. Implied usage is only that it needs product key and rule group ID.

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