ncloud_copy_rule_group

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

Annotations are empty, so the description carries full burden. It discloses the copy operation creates a new rule group, but does not clarify whether the copy is a deep copy (including all rules and settings), whether the source is unaffected, or whether any permissions are required. The write-like nature of the operation is only implied by 'copy' and 'create a new one'.

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 12-word sentence that is front-loaded with the key verb and resource. It contains no filler or redundant information, making it highly concise and scannable.

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?

With only two simple parameters, no output schema, and no nested objects, the tool is relatively simple. However, the description does not specify what the response contains (e.g., new rule group ID) or any behavioral caveats like name uniqueness. It is minimally sufficient but leaves room for more detail about the copy semantics.

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%: both groupName and ruleGroupId have clear descriptions. The tool description adds minimal value beyond the schema, only reinforcing that the source is 'existing' and the new group is 'new'. Since the schema already documents parameter meaning, the baseline 3 applies.

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 ('Copy') and the resource ('Cloud Insight event rule group'), with the explicit purpose of creating a new one. This distinguishes it from sibling tools like ncloud_create_rule_group (which creates from scratch), ncloud_update_rule_group, and ncloud_delete_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?

The description implies the tool is used when you want to duplicate an existing rule group, but it does not explicitly state when to use it over alternatives such as create_rule_group, nor does it mention any prerequisites or constraints (e.g., the source group must exist). No when-not-to-use guidance is provided.

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