ncloud_secret_delete_rotation_trigger

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that: it explains the side effect (rotation can no longer run) and the confirm=true gate, which the annotations do not convey.

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 sentence with the destructive warning front-loaded, followed by the effect in parentheses and the confirm gate. Every clause earns its place and nothing is padded.

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 3-parameter mutation with no output schema and annotations already covering the safety profile, the description supplies the essential missing context: irreversibility of effect on rotation and the confirm requirement. It could note whether the trigger can be re-added, but it is largely complete.

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 confirm parameter is already documented in the schema ('Must be true to actually execute...') along with secretId and keyIsolation. The description only restates confirm=true, adding no semantics beyond the structured data, 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?

States a specific verb (remove) and resource (rotation trigger on a secret) plus the operational consequence ('automatic rotation can no longer run'), which helpfully distinguishes it from disable_auto_rotation. It does not explicitly name sibling alternatives such as ncloud_secret_update_rotation_trigger, so it stops short of full differentiation.

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 'Set confirm=true to execute' line gives a concrete precondition for invocation, and the destructive framing implies caution. However, there is no explicit statement of when to prefer this over ncloud_secret_disable_auto_rotation or ncloud_secret_update_rotation_trigger.

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