ncloud_secret_request_deletion

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

Annotations only declare destructiveHint=true; the description adds substantial context beyond that — the operation schedules deletion rather than removing immediately, it can be reversed via ncloud_secret_cancel_deletion, and execution requires confirm=true. This is exactly the behavioral detail needed for a destructive mutation.

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 sentences, front-loaded with the destructive warning, then the reversibility path, then the confirm requirement. Every clause earns its place with zero filler.

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 destructive, no-output-schema tool, the description covers what gets destroyed, that it is recoverable, how to recover, and the safety gate. Nothing essential to correct invocation 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%, so the schema already fully documents secretId, keyIsolation, and the confirm gate. The description only reinforces confirm=true, adding no syntax or meaning beyond the structured fields — 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 ('Request deletion of a secret') and immediately clarifies the mechanism (scheduled deletion, not immediate removal), which distinguishes it from the sibling ncloud_secret_delete_secret and explicitly names ncloud_secret_cancel_deletion as the alternative. An agent can route correctly without opening any schema.

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?

Gives clear context for use and names the cancel path with the sibling tool, effectively telling the agent this is a soft, reversible request. It does not explicitly state when to prefer this over the hard-delete sibling, so it stops short of full when-not guidance.

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