ncloud_create_rule_group

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

Annotations only include destructiveHint=false, which is consistent but minimal. Description does not disclose behavioral details beyond creation, such as whether the tool is idempotent, returns the created group, or requires specific permissions. There is no contradiction with annotations.

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?

Two sentences – no wasted words. The first sentence states the purpose, the second lists key components. Ideal conciseness for a creation tool.

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 the tool's complexity (7 parameters, 5 required, no output schema), the description is adequate but misses context such as prerequisites (monitorGroupId, metricsGroupId must exist) and behavior on duplicate names. It does not explain that cfgRuleList holds multiple rules, though the schema covers that.

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 clear descriptions for all 7 parameters. The description lists categories of parameters (monitoring targets, metrics, thresholds, notification recipients) but adds no additional meaning or context beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states the action (create), the resource (Cloud Insight event rule group), and the purpose (monitoring alerts). It distinguishes from sibling tools like ncloud_list_rule_groups, ncloud_delete_rule_group, ncloud_update_rule_group, and ncloud_create_rule_directly by specifying that it creates a rule group with monitoring targets, metrics, thresholds, and notification recipients.

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?

Description provides no guidance on when to use this tool versus alternatives (e.g., ncloud_create_rule_directly for single rules) or prerequisites (e.g., existing monitor group and metrics group). Agent must infer from parameter names and schema.

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