ncloud_secret_execute_rotation

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

Annotations are empty, so the description carries the full behavioral burden and it only restates that a job starts. It does not say that the secret value will change, whether a rotation trigger must already be configured, whether the job runs asynchronously against a pending stage, or how it relates to rollback/retry. For a mutation on secret material this is a meaningful gap.

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 short sentence, front-loaded with the action and resource, with the parenthetical adding useful clarification rather than filler. No waste.

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?

With no annotations, no output schema, and a mutation of secret material, the description should at minimum state prerequisites (existing trigger) and the effect on the current secret value. Those are absent, leaving the agent unable to predict consequences or dependencies.

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 keyIsolation enum is documented in detail (global vs regional hosts, JPN caveat), so the schema does the heavy lifting. The description adds nothing about secretId or keyIsolation, 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?

States a specific verb and resource ('Start a rotation job for a secret') with a timing adverb ('now') and parenthetical clarification that it runs the rotation trigger. That is clearer than a bare mutation name, but it never names the closely related siblings (ncloud_secret_retry_rotation, ncloud_secret_cancel_rotation, ncloud_secret_rollback_rotation), leaving the distinction to inference.

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?

'Now' implies an immediate/manual rotation as opposed to the scheduled auto-rotation controlled by enable_auto_rotation, so usage is implied rather than stated. There is no explicit when-to-use/when-not or pointer to sibling commands like retry_rotation or cancel_rotation, so an agent must infer the routing.

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