ncloud_secret_delete_secret

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

Annotations already declare destructiveHint=true, so the warning label is partly redundant, but the description adds genuinely useful behavior beyond the annotation: the two-step 'confirm=true' gate that must be set to actually execute. It also explicitly states the permanence of the effect, which the annotation flag alone does not convey.

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?

Two tight sentences with no waste, warning emoji and the destructive nature front-loaded, and the action requirement second. Every clause 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 single-resource destructive delete with destructive/idempotent annotations and a fully documented schema, the description covers the essentials: permanence and the confirm gate. It could still note the soft-delete alternative (request_deletion) to be fully complete against siblings, but no critical calling information is missing.

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% and every parameter (confirm, secretId, keyIsolation) is already documented in the schema, including the confirm gate and the global/regional host distinction. The description's mention of confirm adds nothing beyond what the schema states, so baseline 3 applies.

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?

States a specific verb+resource ('delete a secret') and adds the crucial qualifier 'Permanently', which implicitly separates it from the sibling ncloud_secret_request_deletion. However, it never names that sibling or any other alternative, so the differentiation is left to inference rather than made explicit.

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 word 'Permanently' hints that this is the hard-delete path versus the request_deletion/cancel_deletion siblings, but the description gives no explicit when-to-use or when-not-to-use guidance or prerequisites. Usage is implied rather than stated.

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