ncloud_nks_get_cluster_addon

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

Annotations already declare readOnlyHint=true, so the description only adds that it returns status, configuration, and version. It does not mention error scenarios or required permissions, but given the annotation coverage, it provides adequate extra context.

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 concise sentence (14 words) that is easy to parse. However, it could be structured with bullet points or sections to improve readability. The conciseness is good but leaves out some useful information.

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 get tool, the description adequately describes the returned data (status, configuration, version). No output schema exists, so the mention of what is returned is helpful. It could mention the format or potential error cases, but overall it is reasonably 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?

Schema description coverage is 100%, so the schema already documents both parameters (addonRef, clusterUuid). The description adds no additional meaning beyond the schema, resulting in a baseline score of 3.

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 tool retrieves a single add-on installed on an NKS cluster, with specific details (status, configuration, version). The verb 'Get' and resource 'add-on' are precise, and it distinguishes from siblings like ncloud_nks_list_cluster_addons or ncloud_nks_get_available_addon.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., for listing all addons use ncloud_nks_list_cluster_addons). The description lacks any context for selection or prerequisites.

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