ncloud_sourcedeploy_get_target_groups

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 the scoping constraint (target groups attached to a specific ASG) but says nothing about return format, pagination, or whether an empty list is possible. With annotations carrying safety, this is a modest addition.

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?

One front-loaded sentence that states verb, resource, and scope with zero filler. Nothing to trim.

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 read-only list tool with full schema coverage and annotation-declared safety, the description is complete enough to invoke correctly. A note on pagination or result shape would have made it fully self-sufficient, but the essentials are present.

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% and the single parameter autoScalingName is already documented with a pointer to ncloud_sourcedeploy_get_autoscaling_groups. The description adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description states a specific verb (Get), resource (list of load balancer target groups), and a scoping relationship (connected to an Auto Scaling group). It distinguishes the tool from the generic ncloud_list_target_groups by scoping results to an ASG, but it does not name any sibling explicitly, so an agent must infer the distinction.

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?

There is no when-to-use, when-not-to-use, or alternative guidance. The purpose statement implies the context (you have an ASG and want its target groups), but with sibling tools like ncloud_list_target_groups and ncloud_get_target_group_detail present, the description never says which to pick.

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