ncloud_add_acg_outbound_rule

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

Annotations include destructiveHint: false, which provides a safety signal. The description adds that this is an additive mutation ('Add'), but does not disclose potential side effects (e.g., whether rules are appended, duplicate handling, or permission requirements). With annotations present, the baseline is lower, and the description adds minimal context beyond the action.

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 sentence with no unnecessary words. It is appropriately terse 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 moderate complexity (7 params, mutual exclusions) and the absence of an output schema, the description only covers the basic purpose. While the schema documents parameters, the description lacks preconditions, expected behavior, or result information, leaving important gaps for an agent.

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?

All 7 parameters have rich descriptions in the schema, including mutual exclusions (ipBlock vs. accessControlGroupSequence) and conditional requirements (portRange for TCP/UDP). The tool description itself adds no parameter information, so it does not exceed the schema baseline.

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 'Add' and a specific resource 'outbound rule to an Access Control Group', clearly distinguishing it from inbound rule tools like ncloud_add_acg_inbound_rule. It precisely conveys the action and target.

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 about when to use this tool vs. alternatives such as ncloud_add_acg_inbound_rule, nor are prerequisites (e.g., existing ACG and VPC) mentioned. The description gives no context for selection.

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