ncloud_set_target_group_description

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

Annotations indicate idempotentHint: true and destructiveHint: false, which the description does not contradict. However, the description adds no behavioral context beyond the annotations, such as what happens if the target group doesn't exist or any length limits on the description.

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 sentence that is direct and to the point. It front-loads the core action without any unnecessary words.

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 simple update tool with two parameters and no output schema, the description is mostly adequate. However, it could be more complete by mentioning prerequisites (e.g., the target group must exist) or constraints (e.g., maximum description length). The annotations help fill the gap slightly.

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?

The input schema provides descriptions for both parameters ('Target group number', 'Target group description'), achieving 100% coverage. The tool description does not add any additional meaning or constraints beyond these basic descriptions, so it adds minimal value.

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 'Set or update the description of a target group' clearly states the verb (set/update) and resource (description of a target group). It distinguishes itself from sibling tools like ncloud_change_target_group_config or ncloud_change_target_group_health by focusing specifically on the description attribute.

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 provides no explicit guidance on when to use this tool versus alternatives. While the purpose is clear, there is no mention of when not to use it or which sibling tools might be more appropriate for different operations. However, the tool name and description implicitly restrict it to description updates.

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