ncloud_secret_list_secrets

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered; the description adds the useful fact that rotation settings and status are included in listings. However, it says nothing about pagination behavior or result limits despite the pageNo parameter, so it only marginally exceeds the annotation's coverage.

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 front-loaded sentence that enumerates the return payload without a wasted word. It is appropriately sized for a simple list tool.

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 safety covered by annotations and fully documented parameters, the description is largely complete, and enumerating return fields compensates for the absence of an output schema. It falls short only on pagination/result-size behavior, which an agent would want for a list operation.

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%, with pageNo and keyIsolation fully documented (including the enum and host-routing semantics), so the schema carries the parameter burden. The description adds no parameter detail beyond what the schema already provides, making the baseline 3 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?

States a specific verb (List) and resource (Secret Manager secrets) and enumerates the returned fields (name, id, type, status, rotation settings), so an agent understands exactly what it retrieves. It does not explicitly name or differentiate itself from sibling readers like ncloud_secret_get_secret or ncloud_secret_get_secret_value, but the listing scope is unmistakable.

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?

The description provides no when-to-use guidance, no prerequisites, and no mention of alternative tools. An agent is left to infer that this enumerates secrets rather than fetching a single value, with nothing steering it toward get_secret/get_secret_value.

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