ncloud_create_asg

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

The description adds the dryRun feature as a preview mechanism, but lacks details on side effects (e.g., resource creation costs, required permissions, or failure states). The annotation only indicates destructiveHint=false, which conflicts with the creation action's mutability, though not directly contradictory.

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 extremely concise with two sentences. The first sentence states the core purpose, and the second provides a key usage note (dryRun). No wasted words.

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?

Given the complexity (13 parameters, 4 required) and lack of output schema, the description is too sparse. It does not mention return values, prerequisites (e.g., existing launch configuration and subnets), or post-creation effects. An agent would benefit from more context about what happens after creation.

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 description does not elaborate on any parameters, but the input schema has 100% coverage with detailed descriptions for all 13 parameters. Baseline 3 is appropriate as the schema carries the full parameter explanation.

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 'Create a new Auto Scaling Group' with a specific verb and resource. Among sibling tools like ncloud_get_asg_detail, ncloud_delete_asg, and ncloud_update_asg, this tool's purpose is distinct and unambiguous.

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 only mentions using dryRun=true for preview, but it does not provide guidance on when to use this tool versus alternative ASG tools (e.g., ncloud_update_asg for modifications). No exclusions or alternative recommendations are given.

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