ncloud_delete_sub_account_access_key

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

Goes well beyond the destructiveHint/idempotentHint annotations by disclosing concrete consequences: irreversibility ('cannot be restored'), immediate impact on clients ('will start failing immediately'), and the confirmation gate required to execute. No contradiction with annotations.

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?

Three dense sentences with zero filler: the destructive warning is front-loaded, consequences are compressed into one clause, and the alternative plus confirm requirement fit in one final sentence. Every element earns its place.

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 3-parameter destructive delete, the description covers everything an agent needs: what is destroyed, the permanence and blast radius, the alternative for non-destructive needs, and the confirmation mechanism. No output schema exists, but return values are not critical for a delete operation.

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 schema fully documents all three parameters including the confirm guardrail and accessKey lookup hint. The description's 'Set confirm=true to execute' reinforces but does not add meaning beyond the schema's own parameter descriptions.

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 states a specific verb (delete), a specific resource (sub account's API access key), and the permanent nature of the action. It actively distinguishes itself from the closest sibling behavior by referencing ncloud_set_sub_account_access_key_status for the non-destructive alternative.

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?

Explicitly states when to use this tool (permanent removal) versus the alternative (temporary disable via ncloud_set_sub_account_access_key_status). Also specifies the mandatory confirm=true guardrail as a precondition for execution.

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