ncloud_secret_update_rotation_period

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

Annotations cover idempotency and non-destructiveness, so the safety profile is partially answered. The description adds nothing beyond intent: it does not say whether rotation must be enabled first, what happens to the current rotation schedule, or whether permissions/KMS isolation affect behavior.

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 front-loaded sentence with no filler and no redundancy. It is efficient, though for a mutation tool the extreme brevity edges toward under-specification rather than pure conciseness.

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 mutating tool with no output schema, the description leaves important context unstated: the precondition that auto-rotation must be active, the effect on existing schedules, and any required auth. Annotations cover part of the safety profile but the agent is left to infer the operational 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?

Schema description coverage is 100%, so secretId, rotationPeriod, and keyIsolation are already fully documented including the 1-730 range and host selection. The description's '(days)' reiterates what the schema already states, adding no new meaning, 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 states a specific verb and resource ('Change the automatic rotation period of a secret') and clarifies the unit in days, so the agent knows exactly what mutation occurs. It does not, however, distinguish this from nearby siblings such as ncloud_kms_update_rotation_period or the enable/disable auto-rotation tools.

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 when-to-use guidance, no statement of preconditions (e.g. that auto-rotation must already be enabled), and no routing to alternatives like ncloud_secret_enable_auto_rotation or ncloud_secret_update_rotation_trigger. Usage is only implied by the tool name.

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