ncloud_secret_retry_rotation

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

Annotations are empty, so the description carries the full behavioral burden and falls short. It does not say whether the retry reuses the original pending stage, whether secrets are modified during retry, what permissions are needed, or whether the operation is safe to invoke repeatedly. The only behavioral hint is the implicit 'failed' precondition.

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 short sentence with no filler and the key qualifier ('failed') front and center. It is efficient, though its brevity contributes to the disclosure gaps noted elsewhere rather than compensating for them.

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 mutation tool with no annotations and no output schema, the description is too thin. It omits prerequisites (job must be failed), effects on the secret, permission requirements, and what the caller gets back, leaving the agent with little to act on beyond a plausible guess.

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 the keyIsolation enum is documented in detail in the schema (global vs regional endpoints, including the JPN caveat), which is more than the description offers. The description adds nothing about parameters, 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?

The description gives a specific verb ('Retry') and a specific resource ('rotation job of a secret') qualified by the precondition that the job failed. That is much sharper than a generic 'retry rotation'. However, it never distinguishes itself from the adjacent siblings ncloud_secret_execute_rotation, ncloud_secret_cancel_rotation, and ncloud_secret_rollback_rotation, which an agent must choose between.

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?

There is no explicit guidance on when to call this versus executing a fresh rotation or rolling back a rotation. The word 'failed' implies a precondition (the job must already be in a failed state) but this is inferred, not stated. No alternatives are named.

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