ncloud_set_targets

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds that the operation replaces all existing targets, which is a key behavioral trait beyond what annotations alone convey. It clarifies that the tool is a full replacement, not a partial update, and does not contradict the annotations.

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, front-loaded sentence with no unnecessary words. It efficiently communicates the core action and the replacement behavior, earning high marks for conciseness.

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 tool has only two simple parameters, no output schema, and annotations covering idempotency and safety, the description provides sufficient context by clarifying the replacement semantics. It does not cover error cases or prerequisites, but it is reasonably complete for the tool's complexity.

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 description coverage is 100%; both parameters already have descriptive comments. The description adds minimal extra semantic value, essentially restating the replacement behavior. Given high schema coverage, baseline 3 is appropriate.

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 the verb 'Set' and the resource 'targets for a target group', and explicitly notes that it replaces all existing targets. This distinguishes it from related sibling tools like ncloud_add_target and ncloud_remove_target, which perform incremental updates.

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 when to use this tool (i.e., when you want to replace all targets) but does not explicitly name alternatives or provide explicit when-not-to-use guidance. The context with siblings suggests that for incremental changes, other tools are appropriate, but this is not stated.

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