ncloud_nks_update_addon

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the agent knows this is a safe, non-destructive operation. The description adds the constraint that at least one of version/configurationValues/resolveConflicts must be provided, which is useful. However, it does not elaborate on response behavior or other nuances.

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 two sentences long, front-loaded with the core purpose, and efficiently conveys the action, resource, and key constraint. No extraneous 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?

Given the tool's moderate complexity (5 parameters, 2 required) and the presence of comprehensive schema and annotations, the description adequately covers the core purpose and constraint. It leaves no major gaps for an agent to misunderstand.

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%, so parameters are thoroughly described in the schema. The description reiterates that version and configurationValues are changeable and mentions resolveConflicts in the constraint, but does not add significant new semantic meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 (update), the resource (add-on on NKS cluster), and what can be changed (version, configurationValues). It includes a necessary precondition (at least one of version/configurationValues/resolveConflicts must be provided). This distinguishes it from sibling tools like ncloud_nks_install_addons or ncloud_nks_delete_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?

The description explicitly states the tool's purpose and the requirement for at least one of the three parameters. While it doesn't explicitly mention alternatives, the sibling list includes install and delete addon tools, providing implicit guidance on when to use this update tool.

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