ncloud_drm_get_license_statistics

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 no further behavioral context such as return format, pagination behavior, or whether results are aggregated or raw records. It does not contradict annotations, but also adds minimal value beyond them.

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-structured sentence that front-loads the tool's purpose and then lists the key filter dimensions. Every word earns its place with no redundancy or padding.

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?

The tool has 8 parameters and no output schema, and the description covers the main purpose and filter types. However, it does not mention pagination parameters (pageNo/pageSize) or clarify whether the response is a list of records or aggregated statistics. Given the complexity and absence of an output schema, this is a noticeable gap.

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 parameters are already documented. The description adds value by grouping the filters into meaningful categories ('content/user/device, time range, status'), which helps agents intuitively map their intent to the available parameters. This goes beyond the schema's individual parameter descriptions.

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 a specific verb ('Get') and resource ('DRM license issuance statistics/history for a site'), and distinguishes this tool from siblings like ncloud_drm_get_site_logs or ncloud_drm_get_policy_logs. The filterable dimensions further clarify the scope.

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 the tool is for querying license issuance history/statistics, but it does not explicitly state when to use it over alternatives or mention exclusions. The context is clear enough for a straightforward read-only stats tool, but no alternative guidance is provided.

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