ncloud_list_asgs

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

The description adds the 'current region' scoping context, which is useful. However, it does not disclose pagination behavior, default page sizes, or what fields are returned, and the readOnlyHint annotation already covers the safety profile. No contradictions exist.

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 sentence with a clear verb and object, no filler words. It is front-loaded and efficient.

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 four optional parameters and a readOnly annotation, the description is mostly adequate. It could mention that it returns a list of ASGs and that pagination is supported, but the schema already exposes the parameters and the operation type is obvious. Slightly incomplete regarding return value specifics, hence 4.

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% with descriptions for pageNo, pageSize, autoScalingGroupName, and autoScalingGroupNoList. The tool description adds no parameter-specific details beyond what the schema already provides, so it lands at the baseline of 3.

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' and resource 'Auto Scaling Groups' with a scope of 'current region', clearly distinguishing it from sibling tools like ncloud_get_asg_detail (for a single ASG) and ncloud_create_asg (for creation).

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 provides no explicit guidance on when to use this tool versus alternatives, such as ncloud_get_asg_detail for detailed information or ncloud_list_asg_activity_logs for activity logs. Usage is implied by the name and phrase 'List all Auto Scaling Groups', but no when-not or alternative instructions are given.

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