ncloud_add_placement_group_server

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

The description simply states the action without disclosing additional behavioral traits beyond what the 'destructiveHint: false' annotation already implies. It does not mention side effects, reversibility, or requirements. With the annotation covering the safety profile, the description adds marginal value, so a baseline score of 3 is appropriate.

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 nine words, concisely and front-loaded with the action. Every word contributes to clarity, with no filler or repetition. It is optimally sized for a simple operation.

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 simplicity of the operation (2 parameters, no output schema), the description is adequate at a basic level. However, it does not cover potential constraints (e.g., placement group capacity, server status) or explain the response format. For an agent, this is minimally sufficient but not rich enough to handle edge cases.

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 ('Placement group number' and 'Server instance number to add'), giving 100% coverage. The description does not add extra meaning beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb ('Add') and resource ('a server instance to a placement group'), clearly stating the operation. It distinguishes itself from the sibling tool 'ncloud_remove_placement_group_server' by the opposite action. The tool name and description are aligned, leaving no ambiguity about what it does.

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 guidance on when to use this tool versus alternatives, prerequisites, or any exclusions. For example, it does not mention that the placement group must exist or that the server must not already be in a placement group. This leaves the agent without context for appropriate invocation.

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