ncloud_secret_create_secret

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

Annotations only declare destructiveHint=false, so the description must carry most behavioral burden. It adds that dryRun returns a preview without creating and gives value-size limits — useful beyond the annotation — but omits auth/permission needs, whether creation is immediate, and rotation side effects.

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?

Three short clauses, front-loaded with the operation and followed by the two most consequential parameter notes. No filler sentences; slightly denser would be ideal but it earns its space.

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 13-parameter create tool with no output schema and conditional requirements (kmsKeyTag when USER_MANAGED_KEY, triggerId/autoRotationPeriod when autoRotationYN=Y), the description is thin. It does not need to restate return values, but it leaves the conditional-parameter and region/keyIsolation story entirely to the schema.

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 each parameter is richly documented in the schema (including cross-references to list_protection_keys and list_triggers). The description merely restates secretValue and rotationTargets semantics already present in the schema, 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?

States a clear specific verb+resource ('Create a secret') and immediately adds two parameter-level clarifications. It does not distinguish itself from the many sibling secret tools (e.g. ncloud_secret_update_secret_value, ncloud_secret_job_start), but the core purpose is unambiguous.

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 only usage guidance is 'Use dryRun=true to preview', which is a helpful invocation hint but not when-to-use-vs-alternatives guidance. No mention of prerequisites (KMS key, trigger) or when to prefer the job/stage-based creation flow in siblings.

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