ncloud_nks_install_addons

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

Annotations declare destructiveHint=false, consistent with the install action. The description adds behavioral traits: the tool requires a minimum Kubernetes version (1.36+), and the dryRun parameter allows preview without actual installation. This provides useful context beyond annotations.

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 concise with two sentences. It front-loads the core purpose and version constraint, then adds the dry-run hint. No fluff or redundancy.

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 moderately complex tool with nested parameters, the description is brief and lacks details on return values (no output schema). While the schema covers parameter definitions, the description could reference the listing tool for add-on names and explain conflict resolution. It is adequate but not rich.

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%; all parameters are documented. The description only reiterates the dry-run option ('preview without installing'), which adds minimal value over the schema. It does not explain the addons array structure or configurationValues beyond what schema already provides.

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 installs add-ons on an NKS cluster, specifying a Kubernetes version requirement (k8s 1.36+) and the dry-run option. It distinguishes itself from sibling add-on tools (list, update, delete) by the verb 'install' and the inclusion of preview behavior.

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 provides some guidance by suggesting dry-run for preview, but it does not explicitly state when to use this tool versus alternatives like ncloud_nks_list_available_addons or ncloud_nks_update_addon. The context of k8s 1.36+ implies a prerequisite, but no direct comparison with siblings is given.

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