ncloud_sourcedeploy_get_autoscaling_groups

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

The readOnlyHint annotation already declares this as a safe read operation. The description adds no behavioral details beyond the name, such as response format, pagination, or filtering, so it provides minimal additional value for behavioral disclosure.

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?

A single, concise sentence that is front-loaded with the action and resource. No redundant or extraneous 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 zero-parameter, read-only list tool with a clear name and annotations, the description is adequate. The absence of an output schema is a minor gap—it does not specify what fields are returned—but the simplicity of the operation makes this acceptable.

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?

There are no parameters; the input schema has an empty properties object. Per the rubric, zero parameters gives a baseline of 4, and since there is nothing to document, this score is appropriate.

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 a specific verb ('Get the list') and clearly identifies the resource ('Auto Scaling groups for SourceDeploy stage configuration'). It distinguishes this tool from general ASG tools like ncloud_list_asgs and other SourceDeploy getters (e.g., get_servers, get_k8s_clusters) by specifying the context of use.

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 when configuring SourceDeploy stages, but it does not explicitly state when to use this tool over alternatives (e.g., ncloud_list_asgs for general ASG listing) or mention any exclusions. Usage context is implied but not directly addressed.

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