ncloud_remove_acg_outbound_rule

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

Although destructiveHint annotation already signals destructiveness, the description adds value by explicitly warning with ⚠️ and highlighting the confirm=true gate required to execute. This goes beyond the annotation, though it does not elaborate on idempotency or side effects.

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 that front-loads the warning, states the action, and gives the essential confirm instruction. No wasted words, highly 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?

For a destructive removal tool with comprehensive schema and annotations, the description sufficiently covers the critical operational context (destructive, confirm required). It does not cover success/failure return values or prerequisites, but those are less critical given the simple single-object operation and existing structured metadata.

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%, so the baseline is 3. The description only repeats the confirm=true instruction already present in the schema (property 'confirm'), adding no additional meaning beyond what structured data provides.

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: 'Remove an outbound rule from an Access Control Group.' This specific verb+resource+scope distinguishes it from sibling tools like ncloud_remove_acg_inbound_rule by explicitly naming 'outbound'.

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 provides implicit context (destructive, requires confirm=true) but does not explicitly state when to use this tool over alternatives, mention exclusions, or describe scenarios. It relies on the tool name and schema for context, offering no direct guidance.

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