ncloud_change_target_group_health

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

Annotations indicate idempotentHint true and destructiveHint false, covering the safety profile. The description adds no additional behavioral context beyond rephrasing the tool name, but it does not contradict the annotations. It could have mentioned immediate application or side effects, but annotations carry most of the burden.

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, compact sentence that is clear and free of unnecessary words. It fully and accurately conveys the tool's purpose without 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?

Given the rich schema and annotations, the description is minimally adequate but lacks context on prerequisites, whether at least one health check parameter must be provided, or the impact of the change. Without this, an agent might invoke it incorrectly (e.g., with no parameters other than targetGroupNo).

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 descriptive documentation for all parameters (100% coverage). The tool description itself adds no parameter-level meaning beyond what the schema already contains, so the schema carries the semantic weight.

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 precisely states that it changes target group health check configuration, using a specific verb and resource. It clearly distinguishes this from sibling tools like ncloud_change_target_group_config, which likely modifies broader target group settings.

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?

No usage guidance is provided. The description does not explain when to use this tool versus alternatives like ncloud_change_target_group_config or ncloud_set_target_group_description, nor any prerequisites or conditions for invoking it.

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