ncloud_delete_placement_group

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

The annotations already declare destructiveHint: true and idempotentHint: true, so the description's '⚠️ Destructive' label repeats that. However, it adds behavioral context by stating 'permanently' and explicitly requiring the confirm flag to be set to true for execution, which is a critical safety guardrail. The description does not contradict the annotations and adds the confirm requirement on top of the schema.

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 two sentences long and immediately conveys the core action and safety condition. The warning emoji and 'Destructive' label are efficient and the confirm instruction is direct. No unnecessary words are used.

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 simple nature of the tool (two parameters, no output schema), the description covers the essential action and the critical confirm guardrail. It does not mention any prerequisites or side effects (e.g., whether the placement group must be empty), but the presence of annotations and schema coverage mitigates the need for more detail. Overall, it is sufficiently complete for an agent to invoke correctly.

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 descriptions for both parameters (confirm and placementGroupNo), covering 100% of parameters. The description adds no additional parameter semantics beyond restating the confirm requirement, so the parameters are adequately documented but not enhanced.

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 purpose: 'Permanently delete a placement group.' The verb 'delete' and object 'placement group' are specific, and the warning icon distinguishes it as a destructive operation. It is unambiguous and differentiates well from sibling tools like ncloud_remove_placement_group_server, which removes servers rather than deleting the group.

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 clear context for when to use the tool (to permanently delete a placement group) and gives an explicit execution requirement: 'Set confirm=true to execute.' It does not, however, explicitly mention alternatives or exclusions, such as noting that removing a server from a group uses a different tool. The destructive nature is highlighted, which serves as a cautionary guideline.

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