ncloud_secret_rollback_rotation

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

Annotations already declare destructiveHint=true, and the description adds substantive context beyond that: it states the warning, explains that the previous value is restored, and reveals the mandatory confirm flag. It does not state irreversibility limits, permission requirements, or timing/state prerequisites, but the added context is meaningful.

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 short sentences, with the destructive warning front-loaded ahead of the execution instruction. No filler, no redundancy.

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 3-parameter mutation tool with no output schema and an annotation already covering destructiveness, the description supplies the key operational facts (what it does, the confirm gate, the effect on the active value). It falls short only on state prerequisites and error/edge behavior.

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 all three parameters (secretId, keyIsolation, confirm) are fully documented downstream; this sets the baseline at 3. The description only restates confirm=true, adding no syntax or value semantics beyond what the schema provides.

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 ('Roll back the last rotation of a secret') and clarifies the observable effect ('the previous value becomes active again'). It is clearly distinguishable in intent, but does not explicitly contrast itself with closely named siblings like ncloud_secret_retry_rotation or ncloud_secret_cancel_rotation.

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 only guidance is the invocation gate 'Set confirm=true to execute'. There is no when-to-use vs when-not, and no routing to sibling rotation tools (retry, cancel, execute), leaving the agent to infer the selection criterion.

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