ncloud_get_contract_usage_list_by_daily

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

readOnlyHint=true already establishes this as a safe read, so the bar is lower. The description confirms it returns per-contract daily data but says nothing about pagination behavior (pageNo/pageSize exist) or result shape; the 3-month cap it mentions is already stated in the schema's param descriptions.

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, zero filler, and the core action is front-loaded before the scoping detail. Every clause carries information.

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 12-parameter read tool with no output schema, the description is quite thin: it omits pagination expectations, how contract identity is scoped (contractNo vs memberNoList vs isPartner/isOrganization), and how it differs from the non-daily usage sibling. The rich schema compensates partially, but the definition leaves real gaps.

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 all 12 parameters are documented in the schema itself, which sets baseline 3. The description only echoes the date-range/3-month concept and adds nothing about isPartner, isOrganization, memberNoList, or the enum-driven productItemKindDetailCode usage.

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 and resource ('Get daily contract usage list') and clarifies the output granularity ('daily usage breakdown per contract for the specified date range'). However, it never differentiates from the sibling ncloud_get_contract_usage_list (the non-daily variant), so an agent must infer which one to call.

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 'max 3 months' note is a constraint the schema already states, not selection guidance. There is no explicit when-to-use-this-vs-alternatives, even though ncloud_get_contract_usage_list, ncloud_get_contract_summary_list and ncloud_get_contract_demand_cost_list are obvious near-neighbors.

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