ncloud_create_login_key

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

Annotations only provide destructiveHint: false, so the description carries the burden. It discloses that the tool is a write operation (create) and importantly that it returns the private key, which is a critical behavioral trait for security. However, it does not mention that the private key is typically only returned once, which is common for key creation tools.

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 extremely concise at one sentence, front-loading the key action and return value. There are no redundant words, and every part of the sentence is informative.

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 tool with one parameter and no output schema, the description adequately covers the main functionality and return value. It could be slightly improved by noting that the private key is only returned once (common security practice), but otherwise it is complete.

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 has 100% coverage with a single parameter 'keyName' described as 'Name for the new login key'. The tool description does not add any additional meaning or constraints beyond what the schema already provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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 that the tool creates a new login key and returns the private key. It is specific about the verb (create), resource (login key), and the return value (private key), distinguishing it from sibling tools like ncloud_list_login_keys, ncloud_import_login_key, and ncloud_delete_login_keys.

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 does not explicitly state when to use this tool versus alternatives. While the purpose is clear from the name and description, there is no guidance on prerequisites, when not to use it, or scenarios where sibling tools might be more appropriate. For a simple create operation, this is adequate but lacking explicit usage context.

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