ncloud_delete_metrics_group_by_id

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

Annotations already indicate idempotentHint=true and destructiveHint=true. The description adds that the tool deletes a rule template, but does not disclose additional behavioral traits beyond the annotations. No contradiction with 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?

Description is a single sentence with a warning emoji, concise and front-loaded. No unnecessary 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 adequate for a deletion tool with good annotation and schema coverage. However, it could mention that the 'confirm' parameter must be set to true to execute, and clarify the scope (Cloud Insight rule template). No output schema needed for this operation.

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?

Input schema has 100% description coverage, so each parameter is already documented. The tool description does not add extra meaning beyond the schema, such as clarifying the 'confirm' parameter's purpose or acceptable values.

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?

Description clearly states the action (delete), the resource (Cloud Insight rule template/metrics group), and the required identifiers (product key and metrics group ID). However, it does not explicitly differentiate from similar sibling tools like ncloud_delete_metrics_group or ncloud_delete_metrics_group_force.

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?

Description mentions that the tool is destructive but provides no guidance on when to use this specific tool versus alternative deletion tools (e.g., ncloud_delete_metrics_group, ncloud_delete_metrics_group_force). No context on prerequisites or conditions for safe use.

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