ncloud_delete_metrics_group

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

The description redundantly restates the destructive nature already indicated by the 'destructiveHint' annotation. It fails to disclose the safety mechanism (the 'confirm' parameter) or any side effects, such as the impact on associated resources.

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 (one line), but it sacrifices useful information for brevity. It earns points for front-loading the destructive alert but loses them for omitting essential details.

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 operation with a mandatory 'confirm' parameter, the description is incomplete. It does not explain the confirm parameter's role, nor does it describe the return value or consequences, leaving the agent with insufficient context.

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 already has 100% description coverage for both parameters. The description adds no further information about the parameters, so it does not improve upon the schema baseline.

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 verb 'Delete' and the resource 'Cloud Insight rule template (metrics group)', making the action unambiguous. However, it does not differentiate from similar sibling tools like ncloud_delete_metrics_group_by_id or ncloud_delete_metrics_group_force, which share the same purpose.

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 is provided on when to use this tool versus its alternatives, nor does it mention prerequisites or the mandatory 'confirm' parameter. The agent is left to infer usage context.

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