ncloud_get_contract_usage_list_by_daily

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the behavioral detail that results are broken down per contract, which goes beyond the name, but it does not describe pagination, response envelope, or any role/privilege nuances.

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 two concise sentences with no filler. It front-loads the main action and then states the key output detail, earning high marks for efficiency.

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?

With no output schema and 12 parameters, the description could provide more context about response structure or filter behaviors. It covers the core intent but omits pagination behavior and how filters like contractNo, memberNoList, or productItemKindDetailCode interact, leaving some gaps for a complex tool.

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 is not required to detail parameters. It only reiterates the date range constraint (max 3 months) that the schema already documents, adding no extra semantic value 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 uses a specific verb 'Get' with a clear resource 'daily contract usage list' and states the return scope 'per contract' and 'date range (max 3 months)'. It effectively distinguishes itself from the sibling 'ncloud_get_contract_usage_list' by emphasizing 'daily', though it does not explicitly name the alternative.

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 implies usage for retrieving daily usage within a date range and enforces a 3-month limit, which is helpful. However, it does not explicitly state when to use this tool over alternatives like ncloud_get_contract_usage_list or mention any exclusions or prerequisites.

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