ncloud_list_targets

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

The readOnlyHint annotation marks this as a safe read operation, but the description adds no additional behavioral context beyond that. It does not disclose potential pagination, response structure, or any side effects. With annotations present, the description should add value beyond the annotation, which it fails to do.

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 concise sentence that conveys the essential action without any unnecessary words. It is well-structured and immediately readable.

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 one parameter, the description is minimally adequate. However, it lacks information about the output (e.g., what list items look like) and does not mention any limitations or result ordering, which could be helpful but is not critical given the tool's simplicity.

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 schema covers the single parameter 'targetGroupNo' with a description 'Target group number', achieving 100% schema coverage. The description does not add any extra meaning to the parameter beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 clearly states the action (List), the resource (targets), and the scope (in a specific target group). It distinguishes itself from sibling tools like ncloud_list_target_groups or ncloud_remove_target by specifying 'targets' within a group, matching the tool name precisely.

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 does not provide any guidance on when to use this tool versus alternatives, such as ncloud_get_target_group_detail or ncloud_set_targets. There is no mention of prerequisites, filtering, pagination, or when this tool is appropriate.

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