ncloud_kms_rotate_key

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

No annotations are provided, so the description carries the full burden. It states the operation but does not disclose what happens to the old key version, whether rotation is reversible, or if the new version becomes primary. For a security-critical mutation, more behavioral context is needed.

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?

The description is two short sentences, front-loaded with the verb and resource. Every word adds value; no fluff.

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?

Given the complexity of key rotation, the description lacks details about return values, effect on key versions, prerequisites beyond 'only enabled keys', and post-rotation state. No output schema or annotations, so the description should provide more context.

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?

The sole parameter keyTag is fully described in the schema ('Key tag - unique identifier derived from key name'). The description does not add further meaning beyond what the schema already provides. With 100% schema coverage, baseline 3 is appropriate.

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 clearly states the action 'Rotate an active key' and the result 'create a new version', with a precondition 'Only enabled keys can be rotated.' This distinguishes it from sibling tools like ncloud_kms_enable_auto_rotation, which is for automatic scheduling.

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 description provides a precondition ('Only enabled keys can be rotated') but does not explicitly guide when to use this tool vs alternatives like enabling auto-rotation or disabling keys. Usage context is implied but not fully stated.

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