ncloud_cm2_register_private_key

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

The only annotation is destructiveHint=false; the description adds substantial behavioral context the annotations do not cover: the main-account-key requirement, the resulting HTTP 403 for Sub Account keys, and the public-zone-only scope. This is exactly the kind of auth/failure disclosure that helps an agent avoid a guaranteed-failing call.

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?

Front-loads the purpose, then adds scope and auth constraints in two compact supporting sentences. The provenance clause ("confirmed by Ncloud support; verified 2026-10-02 with NCP_ADMINISTRATOR") is slightly chatty but lends credibility to the 403 claim.

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 2-parameter mutation tool with no output schema and only a destructiveHint annotation, the description covers purpose, zone scope, and the key auth failure mode. Nothing critical to calling it correctly appears to be missing.

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 coverage is 100% and both parameters (certificateNo, privateKey) are fully documented in the schema, so the description has no obligation to add meaning. It provides nothing beyond the schema, which is the baseline-3 case.

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 ("Register") and resource ("the private key for a certificate that was issued from an external CSR"), which an agent can act on. It is distinguishable from the similarly named ncloud_cm2_register_external_certificate, though the differentiation is implied rather than stated explicitly.

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?

Gives concrete applicability conditions ("Public zone only", requires a main-account API key, Sub Account keys get HTTP 403) that directly determine whether a call will succeed. It does not name alternative tools or explicit when-not scenarios, so it stops short of full routing guidance.

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