ncloud_ses_get_login_keys

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

Annotations already declare readOnlyHint=true. The description confirms it is a read operation ('Get...') but adds no additional behavioral context such as authentication requirements, response size, or pagination. Given annotation coverage, the description adds minimal value beyond confirming safety.

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?

One sentence, front-loaded with the key information, no unnecessary words. Highly concise and well-structured.

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?

The description states the return value is an 'authentication key list' but does not specify the format or exact contents (e.g., key names, fingerprints). For a simple list tool, this is adequate but lacks precision. No output schema exists, so more detail would be beneficial.

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?

There are zero parameters, so schema coverage is 100%. The description correctly refrains from adding parameter details, which is appropriate. For zero-parameter tools, baseline is 4.

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 authentication key list) and the specific resource (SSH access for Search Engine Service manager nodes). This distinguishes it from sibling tools like ncloud_list_login_keys (general login keys) and ncloud_hadoop_list_login_keys (Hadoop-specific).

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 usage context (for SES manager nodes) but does not explicitly state when to use this tool versus alternatives. No when-not-to-use guidance is provided, leaving the agent to infer from the name and siblings.

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