ncloud_get_demand_cost_list

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

With readOnlyHint annotation already indicating a read operation, the description adds valuable context by specifying the output includes discounts, VAT, and payment status, and enforces a 3-month max range. This is sufficient given the lack of an output schema.

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?

Two sentences totaling 26 words, front-loaded with the core purpose. Every word earns its place with 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?

Given the 7 parameters and absence of an output schema, the description is adequate but could be improved. It mentions key output fields but omits pagination behavior or differentiation from sibling cost tools. It provides enough context for basic usage but leaves gaps for complex scenarios.

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 description adds marginal value beyond the schema. It reinforces the date range constraint but does not elaborate on other parameters like pageNo or isPartner. The description does not compensate for missing schema details.

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 retrieves monthly billing cost lists, including discounts, VAT, and payment status. While it does not explicitly distinguish from sibling tools like ncloud_get_product_demand_cost_list or ncloud_get_contract_demand_cost_list, the verb and resource are specific enough for an agent to understand its core purpose.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. Without context on when to choose this over similar billing tools, the agent lacks decision support.

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