ncloud_delete_sub_account

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

The description goes beyond the destructiveHint annotation by detailing consequences: 'All associated permissions and access will be revoked.' It also discloses the confirmation requirement ('Set confirm=true to execute'), which is not present in annotations. This provides valuable safety context for an irreversible operation.

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 highly concise with two sentences. The destructive warning is front-loaded with an emoji, and every phrase ('permanently delete', 'permissions revoked', 'confirm=true') conveys essential information without redundancy.

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 simple delete operation with strong annotations, the description is sufficient. It covers the action, consequences, and the required confirmation flag. It does not describe return values or error scenarios, but these are less critical for a straightforward destructive tool without an output schema.

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%, so both parameters are already documented. The description adds a behavioral note about confirm=true, connecting the parameter semantics to the destructive action. This reinforces the confirmation requirement beyond the schema's default-value description, adding value.

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: 'Permanently delete a sub account'. It uses a specific verb ('delete') and resource ('sub account'), and the warning emoji emphasizes destructive intent. This distinguishes it from sibling tools like ncloud_list_sub_accounts and ncloud_create_sub_account.

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 a key usage guideline: 'Set confirm=true to execute.' This tells the agent the prerequisite for execution. While it doesn't explicitly mention alternatives or exclusions, the confirm-flag requirement is a clear condition for safe usage, which is sufficient for a destructive operation.

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