ncloud_cdss_list_nodes

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

The description is consistent with the readOnlyHint annotation, confirming it is a read-only operation. However, it does not add behavioral details beyond that, such as pagination, permissions, or response characteristics. With an annotation present, a score of 3 is appropriate.

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, efficient sentence that conveys the necessary information without any extraneous words. It is well-structured and front-loaded with the key action.

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?

Despite having no output schema, the description does not provide hints about what the response contains (e.g., list of node IDs, names, status). For a listing tool, this is a significant gap that limits the agent's ability to interpret results.

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?

There is only one parameter (serviceGroupInstanceNo), and its schema description ('Cluster instance number') is clear. The description does not add any extra meaning beyond the schema, meeting the baseline for 100% 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 ('List'), the resource ('nodes in a CDSS cluster'), and specifies the scope ('all nodes (broker, manager)'). This distinguishes it from other CDSS tools like ncloud_cdss_get_cluster_detail or ncloud_cdss_get_node_spec.

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 on when to use this tool vs alternatives. The description does not mention conditions or context that would help an agent decide between this and other CDSS listing tools (e.g., ncloud_cdss_get_broker_info).

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