ncloud_list_asg_activity_logs

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

With readOnlyHint=true already in annotations, the description adds the scoping constraint 'scaling actions', clarifying what kind of logs are returned. It does not disclose additional behaviors such as pagination limits, event retention window, or any authentication prerequisites, but the annotation covers the safety profile.

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?

One sentence with 10 words, front-loaded with 'List activity logs'. It contains no irrelevant details and is optimally concise for a straightforward list operation.

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 tool is simple, but since there is no output schema, the description does not explain what the returned log entries contain (e.g., fields, timestamps). It also omits any default pagination behavior or time range. The essential scope is clear, but for a tool returning data, a bit more detail would make it comprehensive.

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 input schema documents all three parameters with descriptions (100% coverage), including 'Page number for pagination', 'Page size for pagination', and 'Auto Scaling Group number'. The description adds no further parameter meaning, so it relies on the schema – meeting 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 clearly states the verb 'List' and the resource 'activity logs (scaling actions) for an Auto Scaling Group'. It precisely differentiates this from general activity log tools (like ncloud_get_activity_logs) and other ASG management operations by specifying the log scope.

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?

Usage context is implied: use when you need scaling actions for an ASG. However, there is no explicit guidance on when not to use it, nor any mention of alternative tools like ncloud_get_activity_logs or ncloud_list_scaling_policies. The description neither names alternatives nor provides exclusions.

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