ncloud_get_discount_list

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

Annotations already declare readOnlyHint: true, so the safety profile is clear. The description adds that it returns all discounts with specific attributes (validity, amounts), which provides some behavioral context beyond annotations. However, it does not mention default sorting, pagination, or performance implications.

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 extremely concise: two short sentences (15 words) that clearly communicate the tool's function. Every word adds value, no redundancy or filler.

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 straightforward list tool with full schema coverage and readOnly annotations, the description is reasonably complete. It explains what the tool returns (discounts with types, validity, amounts). Could potentially mention that it provides a list of all assigned discounts, but overall it's sufficient.

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 coverage is 100%, so the baseline is 3. The description does not add any additional meaning or context to parameters beyond what is already in the schema. It simply restates the types returned.

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 a list of discounts (product discounts, credits, coins) with validity periods and amounts. The verb 'Get' and the resource 'discount list' are specific. It distinguishes itself from similar sibling tools like 'ncloud_get_product_discount_history_list' by focusing on the current assigned discounts, though not explicitly.

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, such as filtering by discount type or using historical tools. The description only states what it does without context for selection or prerequisites.

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