ncloud_set_region

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

Annotations already convey that the operation is idempotent and not destructive/read-only. The description adds accepted values but does not disclose broader behavioral details such as whether the region change is global or per-session, or affects subsequent calls. With annotations covering the safety profile, this is acceptable but not rich.

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 compact sentence that states the purpose and accepted values with no unnecessary words. It is front-loaded and easy to parse.

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 setter with one parameter, no output schema, and clear annotations, the description is adequate. It explains the parameter format and the operation. It could mention the scope of the change (e.g., global vs. session), but this is not critical given the tool's simplicity.

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?

The input schema provides 100% coverage of the 'region' parameter with explicit mappings (KR: KR-CENTRAL, KRS: KR-SOUTH, 한국, 한국남부). The description loosely repeats this information without adding new semantic meaning, so it does not exceed the schema's clarity.

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's function: 'Set the active Ncloud (Gov) region by code or Korean name.' It uses a specific verb ('Set') and resource ('active region'), and explains accepted input formats (KR, KRS, 한국, 한국남부). This distinguishes it from sibling tools like ncloud_get_current_region or ncloud_get_regions.

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 when to use the tool (when you need to change the active region) but does not explicitly name alternatives or state when not to use it. Context is clear, but no exclusions or comparisons to related region tools are provided.

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