ncloud_get_asg_detail

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

The description's 'Get detailed information' is consistent with the readOnlyHint annotation. However, it does not disclose any additional behavioral traits such as error handling, rate limits, or authentication needs beyond what the annotation already provides.

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 sentence of 9 words, highly concise and front-loaded with the verb 'Get'. Every word serves a purpose, with no redundant or missing information.

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 retrieval tool with one required parameter and no output schema, the description is reasonably complete. It clearly indicates the action and required input. The lack of output schema details is acceptable for a generic tool, and the readOnlyHint annotation covers the operational context.

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 describes the only parameter 'autoScalingGroupNo' as 'Auto Scaling Group number to query', providing full coverage. The tool description does not add extra context like format examples or how to obtain the number, so it meets the baseline without adding value.

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 verb 'Get' and the resource 'detailed information about a specific Auto Scaling Group'. It is distinct from sibling tools like ncloud_list_asgs (list all) and ncloud_create_asg (create), making the purpose easily understandable.

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 for retrieving details of a specific ASG, but it does not explicitly state when to use this tool versus alternatives like ncloud_list_asgs or ncloud_get_asg_activity_logs. No when-not-to-use or alternative tool references are provided.

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