Delete one or more Cloud Insight rule templates (metrics groups) for a product key using IDs; confirmation must be true to execute.
⚠️ Destructive: Delete one or more Cloud Insight rule templates (metrics groups).
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | Must be true to execute deletion. | |
| prodKey | Yes | Product key (cw_key) the metrics groups belong to | |
| metricsGroupIds | Yes | Metrics group IDs to delete |
Changes observed during successful MCP inspections.
v2.0.1Input schema / properties / metricsGroupIdRemoved value: -{
- "description": "Metrics group ID to delete",
- "type": "string"
-}Input schema / properties / metricsGroupIdsAdded value: +{
+ "description": "Metrics group IDs to delete",
+ "items": {
+ "type": "string"
+ },
+ "minItems": 1,
+ "type": "array"
+}Input schema / properties / prodKeyAdded value: +{
+ "description": "Product key (cw_key) the metrics groups belong to",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "metricsGroupId"
-]New value: +[
+ "prodKey",
+ "metricsGroupIds"
+]v1.10.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, and the description's '⚠️ Destructive' merely restates that. It adds the clarification that a metrics group is a Cloud Insight rule template, but omits the schema's confirm=true gate and says nothing about irreversibility or what happens to attached rules.
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?
One short sentence, warning front-loaded, zero filler or 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 destructive, batch-capable delete tool with no output schema, the description leaves the confirmation requirement and the sibling-tool choice to be inferred from the schema and tool list. It is minimally adequate but not self-sufficient.
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 prodKey, metricsGroupIds, and the confirm flag are already fully documented in the schema. The description adds no parameter-level meaning, so the baseline 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?
States a specific verb (Delete) and resource (Cloud Insight rule templates / metrics groups) with batch scope ('one or more'). It does not distinguish itself from close siblings such as ncloud_delete_metrics_group_by_id or ncloud_delete_metrics_group_force, but the core action is unambiguous.
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 when-to-use guidance, no preconditions, and no mention of the alternative deletion tools (by-id, force). An agent has no signal for choosing between the three delete variants.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.