ncloud_cdss_get_node_spec

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

The readOnlyHint annotation already communicates that this is a safe read operation. The description adds the qualifier 'current', which implies it returns live state rather than options, but it does not disclose details like return format, pagination, or whether all nodes are included. This modest addition is consistent with the annotation.

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, front-loaded sentence with no redundant words. It states the verb and object clearly, making it easy to parse at a glance.

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 simple read-only tool with one parameter and a clear purpose, the description is sufficiently complete. It explains what is returned (server spec details for nodes) and the required input (cluster instance). No output schema exists, but the description gives enough context for an agent to invoke correctly.

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% with the single parameter serviceGroupInstanceNo described as 'Cluster instance number'. The tool description does not add further parameter-specific meaning, but it confirms the parameter identifies the cluster for which node specs are retrieved. This matches the schema baseline.

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 a specific verb ('Get') and resource ('server spec details for nodes in a CDSS cluster'), making the tool's purpose unambiguous. It does not explicitly distinguish from sibling tools like ncloud_cdss_get_server_spec_list, but the focus on 'current ... details for nodes' provides enough differentiation.

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 such as ncloud_cdss_get_server_spec_list or ncloud_cdss_get_cluster_detail. The description does not mention any conditions or exclusions, leaving the agent without decision support.

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