ncloud_ses_restart_cluster

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

Annotations declare idempotentHint=true and destructiveHint=false, indicating a safe, non-destructive operation. The description adds no extra behavioral context beyond this, such as whether the restart causes downtime or how long it typically takes. With annotations covering the safety profile, a score of 3 reflects that the description does not add significant value but does not contradict.

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, concise sentence with no superfluous content. It is front-loaded and directly states the action. However, it could be slightly expanded with key context without losing 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?

The description is too minimal for a restart operation. It lacks details on what happens after restart (e.g., job ID, async behavior), whether it affects existing connections, or if a status check is needed. Given the absence of an output schema, the description should provide more operational context.

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 coverage is 100% with a single parameter 'serviceGroupInstanceNo' described as 'Cluster instance number'. The tool description does not add any additional meaning or usage hints beyond what the schema already provides, so 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 uses a specific verb ('Restart') and a clear resource ('Search Engine Service cluster'), which distinguishes it from sibling tools like ncloud_ses_create_cluster or ncloud_ses_delete_cluster. The purpose is immediately apparent.

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?

No guidance is provided on when to use this tool versus other SES cluster operations. There is no mention of prerequisites, such as ensuring the cluster is running, or alternatives like pre-upgrade checks. A minimal description leaves the agent to infer usage context.

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