ncloud_get_metrics_group

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

The description aligns with the 'readOnlyHint' annotation by using 'Get'. No additional behavioral context is provided beyond the annotation (e.g., no mention of return format or limitations). Since the annotation already covers safety, the description adds minimal value.

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, concise sentence that gets straight to the point. It is front-loaded with the action. While it could include more detail, it avoids 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?

Given no output schema, the description hints at 'detailed information' but does not specify what fields or structure to expect. The tool is simple (1 param, read-only), but an agent would benefit from knowing whether it returns configuration, rules, or metrics. It's adequate but not fully informative.

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 coverage is 100% with 'metricsGroupId' described. The description does not add extra meaning to the parameter; it only restates the resource. For high schema coverage, baseline is 3, and no additional clarification is provided.

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 action ('Get detailed information') and resource ('specific Cloud Insight rule template (metrics group)'). It distinguishes from sibling tools like 'ncloud_list_metrics_groups' by implying a single entity. However, the term 'rule template' is slightly inconsistent with the tool name 'metrics group', which may cause minor confusion.

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 versus alternatives. For a getter with a clear listing sibling ('ncloud_list_metrics_groups'), explicit advice to use that for listing all metrics groups would be helpful. This omission makes it hard for an agent to decide confidently.

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