ncloud_kms_enable_auto_rotation

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

The description adds no behavioral context beyond the annotations (idempotentHint=true, destructiveHint=false). It does not disclose effects like whether prior rotation settings are overwritten, or if the operation is reversible. Annotations already cover idempotency and non-destructiveness, but the description does not elaborate.

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 a single sentence that directly states the tool's purpose. It is front-loaded, concise, and contains no extraneous information. Every word is necessary.

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 simple enable operation with one parameter, the description is minimally adequate but lacks context such as prerequisite key existence, relationship to other KMS operations, or typical use cases. It could be improved by noting that the key must already exist and that keyTag comes from ncloud_kms_get_key_list.

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 input schema has 100% description coverage (keyTag described as 'unique identifier derived from key name'). The description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance understanding.

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 'Enable automatic key rotation for a KMS key' clearly states the action (enable) and the resource (automatic key rotation for a KMS key). It distinguishes from sibling tools like ncloud_kms_disable_auto_rotation and ncloud_kms_rotate_key, making the tool's purpose specific and unambiguous.

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 no guidance on when to use this tool versus alternatives (e.g., ncloud_kms_rotate_key for manual rotation, ncloud_kms_disable_auto_rotation to disable). It does not mention prerequisites (e.g., key must exist) or context for using the keyTag parameter.

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