ncloud_cm2_list_advanced_certificates

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

Annotations only supply readOnlyHint=true, so the description carries most of the behavioral burden and does so well: it discloses that Sub Account keys are rejected with HTTP 403 and that a main-account key is required, with corroborating evidence. It stops short of describing pagination defaults or the result shape, so it is not exhaustive.

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-loaded with what is listed and the scope, then the hard constraint. Three tight sentences with no filler, though the provenance tail ("confirmed by Ncloud support; verified 2026-10-02 with NCP_ADMINISTRATOR") is slightly heavier than needed for a simple 403 warning.

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 read-only, fully documented 3-param list tool with no output schema, so the description need not explain returns. It covers scope and the critical auth pitfall; the only gap is not routing the agent among the several sibling cm2 certificate-listing tools.

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% (page, pageSize, certificateName all documented with descriptions), so the schema already does the heavy lifting. The description adds only an oblique reference to "their orders" in the result and gives no extra meaning for the three filter/paging parameters; 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 specific verb and resource (list Advanced paid DV/OV certificates and their orders) and scopes it to Certificate Manager 2.0. The parenthetical "Advanced (paid DV/OV)" distinguishes it from the sibling ncloud_cm2_list_cloud_certificates/ncloud_cm2_list_certificates by certificate class, though it never names those siblings 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?

"Public zone only" and the main-account key precondition give usage context, so an agent knows the eligible environment. However, there is no explicit when-to-use/when-not statement or named alternative, leaving selection between this and the other cm2 list-certificate tools to inference from the certificate-type qualifier.

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