ncloud_delete_metrics_group

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

Annotations already declare destructiveHint=true, and the description merely reiterates 'Destructive' with an emoji. It adds a small clarification that the target is a rule template but does not disclose irreversibility, effect on related rules, or that explicit confirmation is required. No contradiction with annotations, but limited extra behavioral context.

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?

A single, front-loaded sentence with a warning symbol. Efficient and free of filler; every word conveys meaning.

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?

As a destructive delete operation, the description is minimal but the schema and annotations fill critical gaps (parameter semantics, destructive flag). Missing usage differentiation and confirmation details are the main shortcomings, making it adequate but not comprehensive.

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%, and both metricsGroupId and confirm are clearly described in the schema. The description adds no extra parameter meaning, so the baseline score 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 uses a specific action ('Delete') and clearly identifies the resource ('Cloud Insight rule template (metrics group)'). It even clarifies what a metrics group is, making the purpose unambiguous even for agents unfamiliar with Cloud Insight.

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_metrics_group_by_id or ncloud_delete_metrics_group_force. It does not mention the confirm parameter requirement or any prerequisites, leaving the agent without decision context.

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