ncloud_list_targets

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

Annotations declare readOnlyHint=true, so the safety profile is already clear. The description adds the scoping phrase 'in a specific target group' but does not disclose additional behavioral details like return format, pagination, or whether the results include health status. It provides only minimal context beyond the 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, front-loaded sentence: 'List all targets in a specific target group'. It contains no filler, redundancy, or unnecessary detail, making it highly concise and well-structured.

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 one parameter and a read-only annotation, the description is adequate but incomplete. It does not describe what the returned targets will contain (e.g., IDs, IPs, health status) or any pagination/limits. Since there is no output schema, the description should provide more detail about the return values, but it leaves this unspecified.

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?

With 100% schema description coverage, the schema already documents targetGroupNo as 'Target group number'. The description does not add extra semantic details beyond referencing 'a specific target group', so it matches the schema without adding new meaning.

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 targets in a specific target group' clearly states the verb (list), resource (targets), and scope (specific target group). This distinguishes it from sibling tools like ncloud_list_target_groups (which lists the groups themselves) and ncloud_get_target_group_detail (which retrieves details of a single group).

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 implies usage when one needs to enumerate targets within a known target group, but it provides no explicit guidance on when to use this tool versus alternatives such as ncloud_list_target_groups or ncloud_get_target_group_detail. There are no exclusions or alternative recommendations.

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