ncloud_kms_update_rotation_period

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

Annotations already indicate the tool is idempotent and non-destructive. The description adds that it updates the rotation period, which is consistent with the annotations. No additional behavioral traits (e.g., side effects, prerequisites) are disclosed beyond the annotations.

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 efficiently conveys the purpose without any redundant words. It is front-loaded and every word earns its place.

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 update operation with well-documented parameters and annotations, the description is complete enough. It covers the core purpose, and the schema handles parameter details. Minor lack of prerequisites (e.g., key must exist) but overall adequate.

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 for both parameters (keyTag and rotationPeriod). The description does not add any extra meaning beyond what is already in the schema, so it meets the baseline of 3 with no added value.

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 'Update' and the resource 'auto rotation period for a KMS key'. It distinguishes this tool from siblings like ncloud_kms_enable_auto_rotation and ncloud_kms_rotate_key by specifying that it updates the period rather than enabling/disabling rotation or performing a manual 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 description does not provide explicit guidance on when to use this tool versus alternatives like ncloud_kms_enable_auto_rotation or ncloud_kms_disable_auto_rotation. The usage context is implied by the tool name and description but lacks explicit when-to-use or when-not-to-use instructions.

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