ncloud_get_product_list

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

Annotations already cover the safety profile (readOnlyHint=true), and the description adds genuinely useful behavior: default page size 50, server-side sort by productCode, and the response envelope (totalRows/returnedRows/hasMore/nextPageNo) with instructions to follow nextPageNo. That is substantial pagination transparency beyond the annotation, though rate limits/quotas are unstated.

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?

Front-loaded purpose sentence, then return contents, filters, and pagination in a logical progression. Dense but every sentence carries information; only minor redundancy between the pagination prose and the pageNo/pageSize schema descriptions.

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?

No output schema exists, so the description correctly compensates by naming the returned fields and the pagination metadata fields. For a read-only list tool with fully documented params, the agent has what it needs to invoke and page 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%, so the schema already documents all 8 parameters with formats and the enum for productItemKindDetailCode. The description only restates that regionCode is required and that optional filters narrow results, adding little syntax or semantics beyond the schema. Baseline 3 applies.

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?

States a specific verb+resource: getting the product/service list for billing, and lists what comes back (codes, names, descriptions, categories). It is broadly distinguishable from service-specific siblings only via the 'for billing' scope, but it never names an alternative, so it falls short of a 5.

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?

Gives usage mechanics ('Use regionCode and optional filters to narrow results') but no when-to-use/when-not guidance and no routing to alternatives such as ncloud_get_product_category_list or the many per-service product tools (ncloud_get_mysql_products, ncloud_apigw_list_products). Implied usage only.

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