ncloud_list_monitor_groups

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

Annotations declare readOnlyHint=true, and the description is consistent. It adds the product-scoping context but does not disclose response format or pagination, which could be relevant for a list tool. The safety profile is covered by the annotation, placing this at baseline.

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?

Single sentence, front-loaded with action verb, no redundant 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?

Simple list tool with one well-documented parameter and read-only annotation. The description adequately states the return type and scope. No output schema exists, but for a simple list, this is sufficient. Could be improved by mentioning response structure, but not necessary.

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 description coverage is 100%, and the prodKey parameter is fully described with context (cw_key, required, use ncloud_get_schema_keys). The description's 'for a specific product' adds minimal value 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 uses a specific verb ('Get the list') and resource ('Cloud Insight monitoring target groups') with a scope ('for a specific product'), clearly distinguishing it from tools like ncloud_get_monitor_group (singular) or ncloud_list_metrics_groups.

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 a listing operation but does not explicitly state when to use this over alternatives like get_monitor_group or create_monitor_group. It does provide a prerequisite by referencing ncloud_get_schema_keys in the parameter description, but that is in the schema, not the description.

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