ncloud_ses_get_node_products

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

The readOnlyHint annotation covers the safety profile, and the description consistently indicates a read operation ('Get'). It adds the G2 scope and product code context, but does not disclose further behavioral details such as pagination or response format. With annotations present, this level is acceptable but not extensive.

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, tightly worded sentence that front-loads the core action and includes the service and generation context. No unnecessary information is present.

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 lookup with one required parameter, the description provides the service (SES), generation (G2), and output type (product codes). It does not need to explain return values since it's a straightforward list and there is no output schema. Slightly more context about the output structure could be added, but it is largely complete.

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 fully describes the single parameter (softwareProductCode) with a cross-reference to getOsProductList, achieving 100% coverage. The description itself does not add new parameter details, but the schema already carries the semantic load. Baseline of 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 tool retrieves available node server types (product codes) for Search Engine Service (G2), using a specific verb and resource. It distinguishes itself from related tools like ncloud_ses_get_server_specs by explicitly mentioning 'product codes', though it does not fully delineate when each should be used.

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 does not explicitly state when to use this tool versus alternatives, but it does mention the prerequisite parameter source ('from getOsProductList'), implying a workflow. This provides some contextual guidance but no explicit alternatives or exclusions.

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