ncloud_secret_cancel_deletion

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful framing that a deletion request must be pending, but does not say what state the secret returns to or that it becomes permanently undeletable/active again.

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?

A single, front-loaded sentence with no filler. It is efficient, though perhaps too lean given the tool's precondition.

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?

Adequate for a simple 2-parameter tool: annotations carry safety, schema carries params, and no output schema exists. The missing piece is the precondition that a deletion request must already be pending, which the description only hints at.

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%; secretId even points to ncloud_secret_list_secrets and keyIsolation thoroughly documents the host-selection enum. The description adds nothing beyond the schema, so the 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 ('Cancel') and resource ('pending deletion request of a secret'), so the operation is unambiguous. It does not, however, distinguish itself from near siblings like ncloud_secret_request_deletion or ncloud_secret_cancel_rotation, which share the secret/deletion domain.

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?

No when-to-use guidance and no alternatives named. The 'pending' qualifier weakly implies the precondition (a deletion must have been requested first, via ncloud_secret_request_deletion), but the description never states this or routes the agent to the inverse tool.

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