ncloud_list_launch_configs

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

The description states it lists launch configurations, which is consistent with the readOnlyHint annotation. It adds that the listing is scoped to the current region, but does not disclose pagination, ordering, or other behavioral traits beyond what annotations already provide.

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, efficient sentence that front-loads the verb and resource. Every word earns its place with no redundancy.

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?

The description covers the core purpose and region scope but omits mention of pagination (though parameters are present) and the exact return type. Given the presence of optional pagination parameters, additional context would be beneficial.

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%, so parameters are fully documented in the schema. The description adds no additional meaning about the parameters, which is acceptable when schema coverage is high.

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 tool lists all launch configurations for Auto Scaling in the current region. It uses a specific verb ('List all') and resource ('launch configurations for Auto Scaling'), and the scope is explicit. It distinguishes well from sibling tools like 'get_launch_config_detail' and 'list_asgs'.

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 this tool versus alternatives (e.g., get_launch_config_detail for a single configuration). The description is neutral, and the context of sibling tools provides implicit differentiation, but the description itself does not offer usage recommendations.

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