ncloud_sourcedeploy_get_autoscaling_groups

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

The description is consistent with the readOnlyHint annotation, indicating a safe read operation. It adds the context of SourceDeploy but does not disclose any additional behavioral traits like pagination, response structure, or limitations. For a simple list tool, this is adequate but not enriched.

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 concise sentence that conveys the core purpose. It is front-loaded and efficient, though it could include a brief note about intended use within SourceDeploy workflows without adding significant length.

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 tool's simplicity (no parameters, no output schema, readOnly annotation), the description sufficiently covers its purpose and context. It specifies the scope (SourceDeploy stage configuration), which is relevant. However, it does not mention any related tools or usage patterns that might be helpful.

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?

With zero parameters and 100% schema coverage, the description does not need to explain parameters. It correctly implies no inputs are required, which is clear from the schema. No additional semantic value is needed.

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', the resource 'Auto Scaling groups', and the context 'for SourceDeploy stage configuration'. This distinguishes it from other sibling tools like ncloud_get_asg_detail which focuses on a specific ASG, though it could be more explicit about what 'available' means.

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 on when to use this tool vs alternatives (e.g., ncloud_get_asg_detail, ncloud_sourcedeploy_get_target_groups). It does not mention prerequisites, exclusions, or context for choosing this tool over others.

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