ncloud_cdss_get_server_spec_list

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

The readOnlyHint annotation already covers the safety profile, so the bar is lower. The description adds that only G3/KVM specs are returned, which is useful filtering context. However, it does not disclose additional behavioral details such as return format, pagination, or any required auth context beyond what the annotation provides.

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 of 8 words. It is front-loaded with the action and resource, and every word adds value. No filler or redundancy.

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 no-parameter, read-only list tool, the description is adequate. It identifies the domain (CDSS) and the specific generation/hypervisor (G3/KVM). The absence of an output schema means return values are not described, but for a simple spec-list tool this is a minor gap. The readOnlyHint annotation covers the safety aspect.

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 and the schema coverage is 100% (empty schema), so there are no parameter semantics to document. The description appropriately does not invent any parameters, meeting the baseline for a zero-parameter tool.

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' and the resource 'server specs', scoped to 'CDSS (G3/KVM)'. This distinguishes it from sibling tools like ncloud_cdss_get_server_generations (generations vs specs) and ncloud_cdss_get_node_products (products vs specs).

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 is provided on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or alternative tools for different scenarios (e.g., when to use ncloud_cdss_get_node_products or ncloud_cdss_get_server_generations instead).

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