ncloud_secret_disable_auto_rotation

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 the operation name: it does not say whether disabling is reversible, whether it clears an existing rotation schedule/trigger, or what permissions are required. With annotations doing the safety work, this terse sentence contributes little behavioral context.

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 padding is appropriate for a simple toggle. It is efficient, though its brevity is partly under-specification rather than pure concision.

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?

The schema and annotations cover inputs and the safety profile, so an agent can call the tool. What is missing is the operational consequence: whether rotation triggers/schedules are removed and whether the action can be undone via ncloud_secret_enable_auto_rotation. Adequate but with a clear gap.

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 documents secretId's source tool and the keyIsolation enum's host-routing semantics in detail. The description adds no parameter meaning of its own, so the baseline 3 for a fully-documented schema 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+resource pair ('Disable automatic rotation of a secret') that an agent can map cleanly to the intended operation. It does not, however, differentiate itself from near-identical siblings such as ncloud_secret_enable_auto_rotation or ncloud_kms_disable_auto_rotation, so the distinction must be inferred from the name.

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 prerequisites, and no mention of the complementary enable_auto_rotation or rotation-period tools. The agent gets only the operation itself, not the condition under which it should pick this tool over its siblings.

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