ncloud_ses_restart_cluster

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds no additional context about the restart behavior (e.g., potential downtime, effect on running jobs, or confirmation requirements). With existing annotations, the description is acceptable but adds no extra transparency value.

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 one concise, front-loaded sentence that clearly states the action and target. No wasted words or redundant information.

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?

The tool has a simple signature with one well-documented parameter, annotations cover safety/idempotency, and the description identifies the resource. Missing output schema is a minor gap, but for a restart operation, the essential information is present.

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% (the sole parameter 'serviceGroupInstanceNo' is described as 'Cluster instance number'). The description does not add any parameter-level information, but the schema already fully documents the required input, so the baseline 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 uses a specific verb ('Restart') and identifies the exact resource ('Search Engine Service cluster'). It clearly distinguishes this tool from sibling operations like delete, create, or upgrade, and matches the tool name precisely.

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. It does not mention prerequisites, situations where a restart is appropriate, or exclude use cases such as other restart operations for different services (e.g., CDSS restart tools).

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