ncloud_secret_update_rotation_trigger

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether replacing a trigger has side effects on pending rotations, whether it requires auto-rotation to be enabled, or what the operation returns.

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 zero filler. It is appropriately sized for a simple setter, though its brevity reflects under-specification rather than earned economy.

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 output schema and multiple similar secret-rotation siblings, the description should at minimum state prerequisites and clarify that this sets the trigger association rather than creating, deleting, or executing one. As written it leaves those gaps open.

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 schema itself is unusually informative (it points to ncloud_secret_list_secrets and ncloud_secret_list_triggers and fully explains the keyIsolation enum). The description contributes no additional parameter meaning, so the baseline of 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?

"Set or change the rotation trigger of a secret" gives a specific verb plus resource, so an agent knows this mutates a secret's rotation trigger. It does not, however, distinguish itself from close siblings such as ncloud_secret_list_triggers, ncloud_secret_delete_rotation_trigger, or ncloud_secret_enable_auto_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?

No when-to-use guidance, no preconditions, and no routing to alternatives. An agent cannot tell from the text whether it must first call ncloud_secret_list_triggers to obtain a triggerId, or how this differs from enabling auto-rotation.

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