ncloud_get_metrics_group

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

The annotation readOnlyHint=true already signals that this is a safe read operation. The description adds no additional behavioral context (e.g., return format, pagination, authentication needs, or any caveats) beyond what the annotation provides. It introduces the term 'rule template' but that is a semantic clarification, not a behavioral trait.

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 is front-loaded with the action and resource. It contains no filler or redundant wording, earning every word.

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 tool has one parameter, no output schema, and simple semantics. The description states the purpose but lacks detail about what 'detailed information' includes (e.g., configuration fields, thresholds, associated rules). Since there is no output schema, the description could have elaborated on the returned content to be more self-contained.

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%: the single parameter metricsGroupId is described as 'Metrics group ID to retrieve details for'. The description adds minimal extra meaning by equating 'metrics group' with 'rule template' and noting 'Cloud Insight', but the schema already conveys the parameter's purpose. Baseline of 3 is appropriate given full schema coverage.

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') and the resource ('specific Cloud Insight rule template (metrics group)'), and uses 'specific' to indicate a single-item retrieval. This distinguishes it from sibling tools like ncloud_list_metrics_groups (list all) and ncloud_get_rules_by_metrics_group (retrieve rules for a 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 implies usage: when you need detailed info about a specific metrics group, identified by an ID. However, it does not explicitly mention alternatives or prerequisites (e.g., obtain the ID via list_metrics_groups). The guidance is minimal and implicit, not explicit.

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