ncloud_edge_add_certificate_to_slot

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

With only destructiveHint=false provided, the description does add some context: the certificate must be of Global Edge Dedicated type and sourced from Certificate Manager, and the target must be an existing slot. However, it doesn't explain whether adding a certificate replaces or coexists with existing ones in the slot, what permissions are required, or what the result is – notable gaps for a mutation tool.

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, well-structured sentence that front-loads the action and the certificate type. No filler, though it is quite terse given it omits any behavioral detail.

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, no-output-schema tool it covers the essentials: what is added, from where, and to what. What is missing is the effect on the slot's existing contents and any precondition, which an agent would likely need before invoking it.

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%, so both slotId and cmCertificateId are already documented. The description reinforces which slot (existing) and which certificate type (Global Edge Dedicated from Certificate Manager) but adds no format or syntax detail beyond the schema. Baseline 3 is appropriate.

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 ('Add') and resource ('a Global Edge Dedicated certificate ... to an existing certificate slot'), and constrains the certificate type and origin (Certificate Manager). This cleanly distinguishes it from siblings like ncloud_edge_remove_certificates_from_slot and ncloud_edge_delete_certificate, though it doesn't name them 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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as ncloud_edge_provision_certificate or how this differs from ncloud_edge_update_certificate_tls. The only implicit usage cue is the tool name itself.

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