ncloud_delete_sub_account

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

Annotations already mark destructiveHint and idempotentHint. The description adds value by explaining that permissions and access are revoked, and that confirm=true is required. This goes beyond the annotations without contradicting them.

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 concise, three sentences, front-loaded with the destructive warning and key details. Every sentence adds value without unnecessary information.

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 no output schema, the description covers the action, consequences, and required confirm parameter. It does not explain idempotency, but that is handled by annotations. For a simple delete tool, this is fairly complete, though prerequisites are 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 description coverage is 100%, with both confirm and subAccountId having clear descriptions. The tool description does not add new parameter semantics beyond what is already in the schema, so baseline score of 3 is appropriate.

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 it permanently deletes a sub account, with a warning icon and details on consequences. It distinguishes from sibling tools like ncloud_create_sub_account and ncloud_list_sub_accounts by specifying the destructive action.

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 explicitly requires setting confirm=true to execute, which is a key usage guideline. However, it does not compare this tool to alternatives (e.g., detaching policies or disabling accounts) to help decide when to use this specific deletion tool.

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