ncloud_list_cache_config_groups

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

The readOnlyHint=true annotation already declares the safety profile, and the description's "List" verb is consistent with it (no contradiction). The description adds minimal behavioral context: "all" states the unfiltered scope and "optionally filtered" implies filter params are optional. However, it discloses nothing about pagination, response size limits, or default behavior — notable gaps for a "list all" operation, though the annotation lowers the burden.

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 front-loaded sentence with zero waste: "List all Cloud Cache config groups, optionally filtered". It is appropriately sized given that the schema fully documents parameters. It is slightly sparse — a sibling-routing hint could have been added without bloat — but as pure efficiency it excels.

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 low-complexity: all 8 parameters are optional with full schema documentation, and the annotation covers the read-only safety profile. However, there is no output schema, and the description says nothing about what the response contains or pagination behavior, which matters for a "list all" operation. Adequate for a simple read tool, but with clear gaps.

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% — all 8 optional parameters are individually documented with descriptions, and the 2 enum parameters specify their allowed values (Redis|Valkey, SIMPLE|CLUSTER). The description's "optionally filtered" merely restates what the schema already implies, adding no meaning beyond it. Baseline 3 applies since the schema carries the parameter documentation burden.

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?

"List" is a specific verb and "Cloud Cache config groups" is a precise resource, so the core action is unambiguous. The "optionally filtered" clause signals the tool's filtering capability. It distinguishes itself from ncloud_create_cache_config_group and ncloud_delete_cache_config_group by verb and from ncloud_list_cache_instances by resource, though it never names these siblings explicitly.

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?

No guidance is given on when to use this tool versus alternatives. Closely related siblings exist (ncloud_list_cache_config_group_versions, ncloud_list_cache_instances, ncloud_get_cache_instance_detail), but the description provides no selection context, exclusions, or conditions. An agent must infer usage entirely from the tool name.

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