ncloud_cm2_list_eab_credentials

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

Goes well beyond the readOnlyHint annotation: it discloses that paging is ignored and every credential is returned (relevant to response size), that only public zones are supported, and that Sub Account keys are rejected with HTTP 403. The auth requirement is exactly the kind of failure mode an agent needs before invoking.

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 purpose first, then behavior, then the auth caveat. Each sentence carries information, though the sourcing tail ('confirmed by Ncloud support; verified 2026-10-02 with NCP_ADMINISTRATOR') is slightly verbose for what is otherwise a tight definition.

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?

With no parameters and no output schema, the description carries the whole burden and covers the key operational facts: no pagination, zone scope, and credential requirements. It does not describe the shape of the returned credential records, but that is a minor gap for a list endpoint.

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?

The tool takes zero parameters, so the schema has nothing to document and the description has no parameter semantics to add. Baseline 4 applies for a parameterless tool.

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 precise verb (List) and resource (ACME External Account Binding credentials) and explicitly scopes it to Certificate Manager 2.0. The verb 'list' cleanly separates it from its siblings ncloud_cm2_create_eab_credential and ncloud_cm2_deactivate_eab_credential without ambiguity.

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 clear applicability context: 'Public zone only' and 'Requires a main-account API key', which tells the agent when the call will and won't work. It does not explicitly name alternative siblings or say when to prefer this over create/deactivate, 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.