ncloud_get_server_specs

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

Annotations already declare readOnlyHint=true, so the description does not need to restate safety. It adds the hypervisor support information, which is beyond what annotations provide. However, it does not disclose other behavioral traits like pagination, rate limits, or authentication needs, so it adds moderate value.

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 two sentences with no wasted words. The first sentence states the main purpose concisely, and the second provides a practical usage hint. It is front-loaded and efficient.

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 complexity (4 parameters, no output schema), the description lacks completeness. It does not mention return value structure, pagination, or common use cases beyond filtering by image. It also does not help the agent differentiate from many similar sibling tools across different services.

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 input schema has 100% description coverage for all 4 parameters, so the description does not need to repeat those. It adds value by connecting serverImageNo to ncloud_get_server_images, but otherwise does not significantly enhance parameter understanding 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 the tool lists available server specifications and mentions hypervisor support (Gen2 XEN, Gen3 KVM). It also indicates a filtering use case with serverImageNo. However, it does not explicitly differentiate from similar sibling tools like ncloud_ses_get_server_specs or ncloud_nks_get_server_specs, so it's not a perfect 5.

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 provides context on when to use the tool (listing specs for XEN/KVM) and a specific usage hint to filter by serverImageNo from ncloud_get_server_images. However, it does not include when-not-to-use or mention alternatives for other services, leaving the agent to infer differentiation from sibling tools.

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