ncloud_ses_get_node_spec_for_change_g3

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

The readOnlyHint annotation already covers the safety profile, and the description adds useful scoping context (G3/KVM, running cluster, changeable specs). However, it does not describe output shape, pagination, or other behavioral details; the annotation carries the main behavioral burden.

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 with no wasted words. The core action and scope are front-loaded, and the sibling alternative is stated efficiently in the second sentence.

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 read-only lookup with 100% parameter coverage and a clear G3/G2 distinction, the description is nearly complete. It does not detail the return shape, but since there is no output schema and the purpose is straightforward, this is a minor gap rather than a blocking one.

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% and both parameters are already explained, including where their values come from. The description adds no significant parameter-level meaning beyond what the schema provides, so the baseline score 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 names a specific verb and resource: get the server specs that a running Search Engine Service cluster's nodes can be changed to. It also distinguishes itself from ncloud_ses_get_node_spec_detail by noting the G3/KVM-only scope and naming the G2 equivalent.

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 states exactly when this tool applies (G3/KVM only) and explicitly routes the agent to the G2 alternative, ncloud_ses_get_node_spec_detail. This gives clear when-to-use and when-not-to-use guidance.

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