ncloud_get_regions

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

Annotations already provide readOnlyHint: true, confirming safe read operation. The description adds the scope 'all available' but does not disclose additional behavioral traits (e.g., regional scope, data freshness). With annotations covering the safety aspect, the description is adequate but not enriched.

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?

A single, concise sentence that is front-loaded with the action verb. Every word is meaningful, with no redundant or extraneous content.

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?

The tool is simple with no parameters and no output schema. The description 'List all available Ncloud regions' is fully complete for the agent to understand the tool's purpose and scope. No additional context is needed.

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 has zero parameters, and schema coverage is 100%. Since there are no parameters to document, the description does not need to add parameter semantics. The baseline for no parameters is 4, and the description appropriately omits irrelevant details.

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 'List all available Ncloud regions' clearly specifies the verb (List), the resource (regions), and the scope (all available). It effectively distinguishes from sibling tools like ncloud_set_region (write) and ncloud_get_current_region (current region).

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 does not explicitly state when to use this tool versus alternatives like ncloud_get_current_region or ncloud_get_zones. Usage context is implied by the verb and resource, but no direct guidance or exclusions are provided.

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