ncloud_update_asg

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

Annotations include idempotentHint and destructiveHint, but the description adds no behavioral context beyond 'update'. It does not disclose whether changes trigger scaling activities, if the update is synchronous, or any permission requirements. With annotations covering safety, the description adds minimal value.

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, front-loaded sentence with no unnecessary words. It efficiently conveys the tool's purpose and example parameters.

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 mutation tool with 7 parameters, no output schema, and no discussion of update behavior or constraints, the description is minimally adequate. It could mention that at least one parameter must be provided, or that the ASG must exist, but it does not.

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 coverage is 100%, so baseline is 3. The description lists example parameters (min/max size, etc.) but adds no new meaning beyond what the schema already provides for each parameter.

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 'Update an existing Auto Scaling Group configuration' clearly stating verb and resource, with examples of parameters. However, it does not explicitly distinguish from sibling tools like ncloud_set_desired_capacity or ncloud_put_scaling_policy, which also modify ASG properties.

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 guidance is provided on when to use this tool versus the many sibling tools. It does not mention prerequisites, constraints, or when to avoid using it. The description is purely functional.

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