ncloud_list_cache_config_group_versions

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds valuable behavioral context about the naming convention and its dependency on instance creation mode, which goes beyond annotations. No contradictions.

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?

Two sentences, front-loaded with the action, every sentence earns its place. No fluff or repetition.

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 list operation with optional filters and readOnlyHint, the description explains the essential naming convention for interpreting results. The absence of an output schema is not a significant gap given the simplicity. Minor omission: no mention of pagination or return format, but not critical here.

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% (both regionCode and cloudCacheDbmsCode have descriptions). The description does not add meaning beyond the schema for these parameters; it only explains the result naming convention, not the parameters themselves. 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+resource ('List available Cloud Cache config group versions') and clearly distinguishes from sibling ncloud_list_cache_config_groups (which lists config groups themselves, not versions). The suffix explanation (simple=Standalone, cluster=Cluster) adds precision.

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?

Provides clear context (suffix must match cloudCacheModeCode used at instance creation) but does not explicitly state when to use this tool over alternatives like ncloud_list_cache_config_groups or ncloud_get_cache_instance_detail. Usage is implied from the name and context, not explicitly contrasted.

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