ncloud_list_target_groups

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

Annotations declare readOnlyHint=true, and the description's 'List' aligns. It adds the 'current region' scope, which is a behavioral constraint not in annotations. However, it does not mention pagination behavior, default page size, or result ordering. Minimal added value beyond annotations.

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 8-word sentence, front-loaded with the verb and resource. There is zero filler or redundancy, earning a top score.

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 tool with readOnly annotation and all parameters documented in the schema, the description adequately covers the operation. The absence of an output schema is offset by the implied return of a list. Missing an explicit note about pagination controls but not critical given schema visibility.

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 covers all five parameters with descriptions (100% coverage), so the description bears no burden for parameter semantics. It does not duplicate or add new parameter details, meeting the baseline expectation for a schema-complete tool.

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 uses a specific verb 'List' with a clear resource 'target groups' and a scope constraint ('in the current region'), which precisely identifies the operation. It distinguishes from siblings like ncloud_get_target_group_detail (single target group) and ncloud_list_targets (targets within groups).

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 explicit guidance on when to use vs alternatives. The implied usage is clear from the name, but there is no mention of exclusions or better-suited tools (e.g., ncloud_get_target_group_detail for a specific group). The description could note that all groups are returned unless filters are applied.

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