ncloud_kms_get_key_list

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds the pagination behavior, which is useful, but does not disclose details such as default page size, ordering, or potential inconsistencies when paginating through a changing dataset. This meets the baseline for a tool with annotation support.

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?

The description is a single, front-loaded sentence with no redundant wording. It wastes no space and directly states the key aspects: action, resource, and pagination.

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 simple read-only listing tool with two optional parameters and no output schema, the description plus schema is sufficient to guide an agent. It identifies the resource and pagination, and the annotations cover side-effect safety. It does not explain return structure, but that is not necessarily required for such a straightforward 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?

The input schema already fully describes both parameters (pageNo, pageSize) with defaults and constraints, so schema coverage is high. The description's mention of pagination adds marginal context but does not go beyond what the schema implies. 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 clearly states the action ('Get'), the resource ('list of all KMS keys'), and the scope ('all'), which distinguishes it from sibling tools like ncloud_kms_get_key_info (single key) and ncloud_kms_get_key_version_list (key versions). This is a specific and unambiguous verb+resource combination.

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 implies this is the tool to call when you need a paginated list of all KMS keys, and the sibling context confirms this is distinct from detail/version/log tools. However, there is no explicit when-to-use or when-not-to-use guidance or named alternatives.

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