ncloud_sourcedeploy_get_servers

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

The readOnlyHint annotation already indicates a safe read operation. The description adds that it returns 'available servers' for stage configuration, but it does not disclose response format, pagination, or what determines availability. This is adequate for a simple list tool but lacks deeper behavioral context.

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 wasted words. It clearly states the action and target, making it highly concise and easy to parse.

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 tool with no parameters and no output schema, the description is reasonably complete: it explains the tool's purpose and scope. However, it does not elaborate on what 'available servers' means or the structure of the returned list, which would be helpful for an agent planning to use the output.

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 tool has zero parameters, so there is nothing for the description to explain. Per the baseline for 0 params, a score of 4 is appropriate since the description adds no parameter information but the schema is fully covered by the absence of parameters.

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 tool 'Get the list of available servers for SourceDeploy stage configuration' with a specific verb and resource. It distinguishes itself from sibling tools by focusing on 'servers' rather than other resource types like autoscaling groups or K8s clusters, though it doesn't explicitly name alternatives.

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 implied usage is for SourceDeploy stage configuration, but there is no explicit guidance on when to use this tool versus alternatives like ncloud_sourcedeploy_get_autoscaling_groups or ncloud_sourcedeploy_get_k8s_clusters. It lacks exclusion criteria or alternative tool references.

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