ncloud_get_server_specs

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

With readOnlyHint: true already declaring the read-only nature, the description adds beyond annotations by noting support for Gen2 XEN and Gen3 KVM, which implies the tool can show specs across different hypervisor generations. This is useful behavioral context not present in the schema.

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, front-loaded with the main action, and no redundant words. Every sentence provides distinct information.

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?

The description is sufficient for a simple read-only listing tool with no output schema. However, given multiple sibling tools with similar names for other services, the description could have explicitly stated that this is for standard Cloud Servers to avoid ambiguity. Otherwise, it's complete.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that serverImageNo should come from ncloud_get_server_images, which gives the agent an actionable way to populate that parameter beyond the schema's generic description.

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, which is a specific verb+resource. It also mentions Gen2 XEN/Gen3 KVM support, adding useful context. It does not explicitly distinguish from sibling tools like ncloud_nks_get_server_specs, but the name and context signal it's for standard servers.

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 gives explicit guidance to use serverImageNo from ncloud_get_server_images to filter compatible specs, which is a concrete cross-tool workflow. It doesn't mention when not to use this tool or alternatives, but the primary usage pattern is clear.

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