ncloud_remove_network_acl_outbound

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

Adds the confirmation gate (confirm=true) beyond the destructiveHint annotation, warning that removal only executes with this flag. The destructive nature is reaffirmed with the warning emoji.

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?

One sentence with warning, front-loaded, every word serves a purpose. No fluff.

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?

The description plus rich schema and annotations cover the action, confirmation requirement, and parameter details. No output schema exists, but for a simple removal operation this is sufficient. Could optionally mention post-condition or reversibility but not critical.

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 descriptions cover all 8 parameters, and the description does not add semantic detail beyond the confirm=true mention already present in the schema. Baseline 3 applies due to 100% schema coverage.

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 uses specific verb 'Remove' and resource 'outbound rule from a Network ACL', clearly distinguishing from the inbound sibling by direction. The warning icon and confirm instruction add operational clarity.

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?

Provides clear context that this targets outbound rules and requires confirm=true, but does not explicitly name the inbound alternative or specify when not to use this tool.

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