ncloud_list_metrics_groups

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

The annotation readOnlyHint=true already indicates a safe read operation. The description does not add extra behavioral context like pagination, rate limits, or default result sizes, so it adds no value beyond the annotation.

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 a single sentence of 13 words, immediately stating the action and resource. No filler or redundant information.

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 simple list operation with one optional parameter and read-only annotation, the description is adequate but missing context to differentiate from similar sibling tools like ncloud_search_metric_list or ncloud_list_rule_groups. No return structure or typical usage hints are provided.

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 has 100% description coverage for prodKey ('Product key to filter metrics groups'). The description mentions the list and implicitly filtering by product key, but does not add any additional parameter semantics beyond the schema.

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 'Get the list' and the resource 'Cloud Insight rule templates (monitoring item groups / metrics groups).' It identifies the tool's purpose but could more precisely distinguish between 'rule templates' and 'metrics groups', which may cause confusion given sibling tools like ncloud_list_rule_groups and ncloud_get_metrics_group.

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?

The description provides no guidance on when to use this tool vs. alternatives such as ncloud_search_metric_list or ncloud_list_rule_groups. No prerequisites, typical use cases, or exclusions are mentioned.

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