ncloud_get_contract_demand_cost_list

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

The readOnlyHint annotation already indicates safe read-only behavior. The description adds context about the 3-month period restriction and the included data fields (usage, pricing, discount). However, it does not mention pagination behavior or what happens if the request exceeds the time limit.

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 a single, well-formed sentence that front-loads the action ('Get contract-level billing cost list') and provides key details without extraneous information. Every phrase earns its place.

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 11 parameters, many optional, and no output schema, the description is somewhat minimal. It adequately states the purpose and main constraints but does not explain the role of key parameters like isPartner, isOrganization, or memberNoList. The schema descriptions fill some gaps, but the description could be more 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?

With 100% schema description coverage, the baseline is 3. The description adds value by emphasizing the 3-month period constraint and summarizing the returned data (usage quantities, pricing, discount amounts), which helps the agent understand the tool's output beyond the schema's parameter definitions.

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 contract-level billing cost list, specifies the return includes usage quantities, pricing, and discount amounts, and notes the 3-month period constraint. This verb+resource+scope combination effectively distinguishes it from sibling tools like ncloud_get_demand_cost_list or ncloud_get_product_demand_cost_list.

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 does not provide explicit guidance on when to use this tool versus its alternatives. It mentions contract-level billing but does not exclude product-level or other cost lists. Given the many sibling billing tools, some usage direction would be beneficial.

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