ncloud_nks_list_available_addons

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

Annotations already mark readOnlyHint: true. The description adds behavioral context: the catalog is available only on 1.36+ clusters, examples of add-ons, and variability by version/region. No contradictions.

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?

Two sentences with front-loaded key action. Could be slightly more structured but is efficient and free of fluff.

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?

Given no output schema, the description provides context about version constraints, regional variation, and example add-ons. It sufficiently covers what the tool does but does not detail output format, which is acceptable for a list tool.

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 coverage is 100% with descriptions for all 3 parameters. The description reinforces the requirement for k8sVersion and its format, adding slight value beyond the schema.

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 lists add-ons installable on an NKS cluster for a given Kubernetes version, distinguishing it from sibling tools like ncloud_nks_list_cluster_addons by specifying 'Add-on Manager catalog' and requiring k8sVersion.

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 explains the requirement for k8sVersion, the version constraint (1.36+), and that available add-ons vary by version and region, guiding usage indirectly. It does not explicitly contrast with alternatives but the purpose is clear enough.

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