ncloud_cm2_list_certificates

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

Annotations only declare readOnlyHint=true; the description adds substantial behavioral context beyond that: main-account API key requirement, the specific HTTP 403 failure mode for Sub Account keys, and the public-zone-only limitation. This is exactly the kind of auth/constraint disclosure that prevents failed calls.

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 purpose, then the comparison, then the key/zone caveats. The trailing verification provenance ('confirmed by Ncloud support; verified 2026-10-02...') is slightly extraneous but the sentence is dense with actionable content.

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 read-only list tool with a fully documented schema and no output schema, the description covers everything an agent needs: scope, alternative, required key type, zone restriction, and response-field value-add. Nothing material is 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%, so page, pageSize, and certificateName are already documented with their own descriptions and constraints. The description mentions page/pageSize but adds no syntax or meaning beyond the schema, 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 specific verb and resource ('List all certificates with paging') and pins the version ('Certificate Manager 2.0'). It explicitly distinguishes itself from the closely-named sibling ncloud_list_certificates (1.0) and names its distinguishing fields (certificate type, status, order).

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 explicit routing guidance: 'For a plain inventory prefer ncloud_list_certificates (1.0, works with any key)' versus when this one is warranted. Adds usage-scoping constraints (public zone only, main-account key required) that tell the agent when NOT to call it.

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