ncloud_get_contract_summary_list

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

The readOnlyHint annotation already indicates this is a read operation. The description adds minimal behavioral context beyond stating it 'returns a summary'. No additional traits like authentication needs, rate limits, or result structure are disclosed.

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 concise sentences: the first states the core function, the second adds key grouping and counting details. 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?

The description adequately covers the tool's primary purpose and grouping dimensions. However, it does not mention optional filters like status, partner mode, or pagination, which are left to the schema. For a read-only summary tool, this is sufficient but not exhaustive.

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 clarifying that regionCode and contractTypeCode are used for grouping, and that contractMonth is the key temporal filter. This provides context beyond 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 specifies the tool's action ('Get contract summary list') and the output format ('grouped by region and contract type with counts'). It distinguishes from sibling tools like ncloud_get_contract_usage_list which focus on usage data rather than summary counts.

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 when a monthly aggregated summary is needed, but does not explicitly state when to use this tool versus alternatives like detailed usage or demand cost tools. No exclusions or when-not guidance is provided.

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