ncloud_list_rule_groups

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

Annotations already declare readOnlyHint=true, so the description's 'Get the list' is consistent. However, it adds no additional behavioral context, such as pagination behavior (though parameters imply it), rate limits, or what happens on empty results. With annotations covering 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?

Single sentence, no filler. Every word is necessary and informative. Highly concise.

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?

Despite complete schema and annotations, the description lacks context for a listing tool: no mention of pagination (though parameters exist), no hint about return format or common use cases. Since there is no output schema, the description should at least indicate that it returns a list or array, which it does not.

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 descriptions for all 4 parameters. The description does not add any parameter semantics or usage hints beyond what the schema provides. Baseline of 3 is appropriate as schema handles documentation.

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 identifies the resource ('Cloud Insight event rule groups') with context ('for monitoring alerts'). It clearly distinguishes from sibling tools like ncloud_get_rule_group (single) and ncloud_create_rule_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?

No guidance on when to use this tool versus alternatives, such as ncloud_get_rule_group for a single rule group or other monitor-group-related tools. The description does not mention when not to use it or provide context about prerequisites or filtering behavior.

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