ncloud_cdss_get_node_spec

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

Annotations already declare `readOnlyHint: true`, so the description adds minimal extra behavioral transparency. It only states 'current' which implies a read operation, but no further details about what happens (e.g., returns spec for all nodes, requires cluster to be active) are disclosed.

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?

One concise sentence that is front-loaded with the action and resource. It could be slightly more informative without losing conciseness, but it is 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?

For a simple read tool with one parameter and no output schema, the description is adequate but does not specify what the 'server spec details' include (e.g., CPU, memory, disk). The agent may need to infer from the name or call the 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?

The schema covers the single parameter completely with a description. The tool description adds no extra meaning beyond the schema, so it meets the baseline for high schema coverage.

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 action ('get') and resource ('current server spec details for nodes in a CDSS cluster'). It distinguishes from siblings like `ncloud_cdss_get_node_products` (which likely gets available node product options) and `ncloud_cdss_get_server_spec_list` (which likely lists available server specs). However, it could be more explicit about what 'current server spec' means in contrast to related tools.

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_node_products` or `ncloud_cdss_get_server_spec_list`. There are no prerequisites or context about the cluster state required.

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