ncloud_get_product_list

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

Annotations already indicate readOnlyHint=true, so the agent knows it's safe. The description adds behavioral details: pagination (default 50/page, sorted by productCode), response fields (totalRows, returnedRows, hasMore, nextPageNo), and the need to follow nextPageNo for complete results. This provides context beyond the annotations.

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 very concise: three sentences that cover purpose, usage, and pagination behavior. It is front-loaded with the core action, and every sentence provides value without 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 complexity (8 parameters, paginated, no output schema), the description covers the essential points: required parameter, optional filters, pagination details, and response fields. It does not detail the exact response structure but lists what data is returned, which is sufficient for most agents. Minor gap: could mention the response format more explicitly, but overall 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?

Schema description coverage is 100%, so the baseline is 3. The description adds minimal additional meaning: it highlights regionCode as required and filters as optional, but the schema already describes each parameter well. The description does not significantly enhance parameter understanding beyond the schema.

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 verb 'Get', the resource 'product (service) list', and the purpose 'for billing'. It distinguishes the tool from siblings by specifying that it returns product details including codes, names, etc., and mentions pagination and filtering, which aligns with this unique billing product listing tool.

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 says to use regionCode and optional filters, but does not explicitly guide when to use this tool versus alternatives like ncloud_get_product_category_list or ncloud_get_product_price_list. It lacks explicit when-to-use or when-not-to-use guidance, making it average in this dimension.

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