ncloud_ses_get_server_specs

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

The readOnlyHint annotation is consistent with the 'Get' operation. The description adds the behavioral constraint 'G3/KVM only', which is beyond the annotation. However, it does not disclose return format or pagination behavior. Since the annotation already signals non-destructive read, the description adds moderate value but no contradictions.

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 sentence that efficiently conveys the tool's purpose and scope. There is no superfluous information, and it is front-loaded with the key action and service.

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?

With low complexity (one parameter, no output schema, annotation present), the description provides sufficient context for the agent to understand the tool's role. The mention of G3/KVM clarifies applicability. The missing output description is mitigated by the absence of an output schema and the tool's straightforward nature.

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 description coverage is 100% for the single required parameter, which already documents its purpose and source (from getClusterServerImageList). The tool description does not add further parameter-specific meaning, so baseline 3 applies.

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 specifies the action ('Get'), the resource ('node server types'), and the service context ('Search Engine Service'). It also adds a scope qualifier ('G3/KVM only'), which distinguishes it from general server spec tools and other SES tools. This provides a specific verb+resource combination.

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 for SES node server types within the G3/KVM scope, but it does not explicitly state when to use this tool versus siblings like ncloud_ses_get_node_products or ncloud_ses_get_cluster_server_images. The parameter description references another tool for obtaining the required product code, offering indirect guidance. No exclusion criteria or alternatives are mentioned.

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