ncloud_ses_get_node_list

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

The annotations already provide readOnlyHint=true, indicating a safe read operation. The description adds no extra behavioral context such as pagination, rate limits, or authentication requirements. It is adequate but does not go beyond what annotations already convey.

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 sentence that is concise and front-loaded with the key verb and resource. Every word serves a purpose, and there is no extraneous 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?

For a simple tool with one parameter and no output schema, the description is minimal but functional. It does not describe the format of the returned node list (e.g., status, specifications) or any pagination behavior, but given the low complexity, it is minimally viable.

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 single parameter (serviceGroupInstanceNo) is described in the input schema as 'Cluster instance number', which is clear. With 100% schema description coverage, the description does not add additional semantics beyond what the schema provides, so baseline 3 is appropriate.

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'), the resource ('node list'), and the context ('for a Search Engine Service cluster'). This is specific enough to indicate the tool's purpose, though it does not explicitly differentiate from sibling tools like ncloud_ses_get_node_spec_detail. The verb and resource are well-defined.

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 (e.g., ncloud_ses_get_cluster_detail, ncloud_ses_get_node_products). There are no prerequisites, exclusions, or references to other tools. The agent receives no help in deciding between this and similar listing tools.

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