ncloud_copy_rule_group

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

The description adequately conveys that the tool duplicates a rule group without modifying the source. However, it does not disclose permission requirements, rate limits, or the scope of what is copied (e.g., all rules and settings). With no annotations, the description carries the burden but is minimally sufficient.

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 with no redundant information. Every word is necessary and front-loaded.

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 simplicity (two parameters, no output schema, no complex behavior), the description is fairly complete. It covers the essential action and the parameters are well-documented in the schema. Minor omission: it does not explicitly state that the source rule group must exist, but that is implied.

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 descriptive parameter names and descriptions. The tool description adds only the context that it operates on 'Cloud Insight event' rule groups, which is already implicit in the schema. 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 tool copies an existing Cloud Insight event rule group to create a new one. The verb 'copy' differentiates it from 'create' or 'update' siblings, but it could be more explicit about the distinction.

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 is provided on when to use this tool versus alternatives like ncloud_create_rule_group. It lacks prerequisites, exclusions, or context about when copying is preferred over creating from scratch.

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