ncloud_nks_get_server_specs

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

Annotations already declare readOnlyHint: true, so the description is not required to state it. The description adds context about being for NKS creation but does not disclose further behavioral traits (e.g., pagination, sorting). It is adequate given the annotations.

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?

Two sentences, no redundancy. Purpose is front-loaded, followed by parameter requirements. Every sentence adds value and is concise.

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 no output schema, the description does not describe the return format or fields. It explains the purpose and input dependencies adequately but lacks information on what the tool returns. Slightly incomplete for a list tool.

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 covers 100% of parameters but the description adds meaning by specifying that softwareCode comes from ncloud_nks_get_server_images and zoneCode/zoneNo are mutually required. This adds value beyond the schema.

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 it lists server specifications for NKS cluster/node pool creation, using a specific verb and resource. It is distinct from sibling tools by the NKS prefix, but does not explicitly differentiate from similar tools like ncloud_ses_get_server_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?

The description explicitly says it requires softwareCode and zoneCode or zoneNo, indicating it should be used after retrieving softwareCode from another tool. It provides clear context on when to use but does not mention when not to use or give alternatives.

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