ncloud_ncr_list_registries

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

The readOnlyHint=true annotation already establishes this is a safe read operation, so the description doesn't need to restate safety. It adds the useful scope detail that results are limited to the current region, but discloses nothing about pagination or result shape, so it's adequate 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?

A single clear sentence with the resource and scope front-loaded and zero filler. Nothing extraneous to trim.

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 read-only list tool with annotations covering the safety profile, fully documented params, and no output schema to explain, the description is nearly complete. The only minor gap is any note on pagination behavior implied by the pageNo/pageSize params.

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%, so pageNo and pageSize are already documented in the schema (including the 'page'/'pagesize' send names and >0 constraints). The description adds no parameter detail, so the baseline 3 applies.

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?

States a specific verb (list) and resource (container registries) with an explicit scope (current region), which distinguishes it from ncloud_ncr_get_registry and the create/delete siblings. The distinction is clear from the standard list-vs-get verb pattern rather than an explicit callout, so it falls just short of a 5.

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?

Usage is implied by the verb 'list' and the phrase 'in the current region', which tells the agent the results are region-scoped. However, there is no explicit when-to-use guidance, no mention of the get/delete/create alternatives, and no note on whether the current region is set elsewhere (e.g., ncloud_set_region).

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