ncloud_remove_target

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

The description adds a prominent destructive warning and specifies the confirm=true safeguard, which goes beyond the annotations' destructiveHint and idempotentHint. This gives the agent actionable knowledge that the operation requires explicit confirmation to execute. No contradiction with 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 sentence with the critical warning front-loaded. Every word earns its place, and it avoids unnecessary elaboration.

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 straightforward destructive operation, the description and schema provide enough context to invoke the tool correctly. The absence of an output schema is acceptable, as return values are not critical for a removal action. The description could optionally mention effects on associated resources, but this is not essential for the core task.

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 already provides full descriptions for all three parameters (confirm, targetNoList, targetGroupNo) with 100% coverage. The description explicitly mentions confirm=true, which aligns with the schema but doesn't add new semantic detail. Thus the baseline score of 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 tool's action ('Remove targets from a target group') with a specific verb and resource. It distinguishes itself from siblings like ncloud_add_target and ncloud_set_targets by focusing on removal. The scope is unambiguous.

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 its usage context by naming the exact operation and the confirmation requirement. However, it does not explicitly contrast with alternative tools such as ncloud_set_targets or ncloud_add_target, so it relies on the tool name and sibling list for differentiation. No exclusions or prerequisites are mentioned, making it clear but not fully prescriptive.

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