ncloud_secret_list_protection_keys

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

readOnlyHint=true already covers the safety profile, so the bar is lower. The description adds that the listed values are kmsKeyTag values usable for USER_MANAGED_KEY protection, which is useful context, but says nothing about scoping effects of keyIsolation, result size, or whether the list is account-wide.

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 no padding; the parenthetical is terse. It is efficient but slightly cryptic, so not quite exemplary.

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?

A one-parameter read-only list tool with a fully documented schema and annotations is largely self-sufficient. Still, with no output schema and no description of the returned structure or pagination, the definition leaves some gaps for correct invocation.

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 in the schema itself (host endpoints, JPN caveat). The description adds no parameter meaning beyond that, 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?

Specific verb (List) plus a precise resource (KMS keys that can protect/encrypt secrets), and it even names the returned field shape (kmsKeyTag values for USER_MANAGED_KEY). It does not, however, explicitly distinguish itself from close siblings like ncloud_kms_get_key_list or ncloud_secret_update_protection_key, so an agent must infer the relationship.

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 is given: the description never says this should be called before ncloud_secret_update_protection_key, nor how it differs from ncloud_kms_get_key_list. The only hint of usage is the implicit 'list' semantics in the name.

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