ncloud_get_product_list

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

Annotations already declare readOnlyHint=true, and the description aligns with a read-only operation. Beyond annotations, it discloses important behavior: pagination details (default 50/page, sorted by productCode, response fields totalRows/returnedRows/hasMore/nextPageNo, and instruction to follow nextPageNo). This adds significant context for handling results correctly.

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 compact and front-loaded: first sentence states purpose, second lists return content, third gives usage and pagination. Every sentence contributes value; no filler or redundancy.

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?

Given the tool has no output schema, the description adequately covers return values (product codes, names, descriptions, categories) and pagination mechanics. The schema covers parameter details, and annotations cover safety, leaving no major context gaps for an agent to invoke this tool 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 description coverage is 100% with each of the 8 parameters fully described (e.g., regionCode 'KR, KRS', productName substring matching). The description only repeats the high-level 'use regionCode and optional filters' without adding parameter-level meaning, so the 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 it 'Get product (service) list for billing,' using a specific verb ('Get') and resource ('product list'), and distinguishes it from sibling product-list tools by scoping it to billing. It also enumerates returned fields (codes, names, descriptions, categories), leaving no ambiguity about its core function.

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 gives clear usage guidance: 'Use regionCode and optional filters to narrow results' and mentions pagination behavior. It establishes the billing context but does not explicitly name alternatives or exclusions (e.g., when to use ncloud_get_product_category_list instead), so it falls short of full differentiation.

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