ncloud_reboot_server

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description is not burdened with the full safety profile. It adds the prerequisite that instances must be running and that multiple servers can be included, but it does not disclose potential downtime or whether the reboot is graceful. This is adequate given the 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, front-loaded sentence that directly states the action, resource, and scope. There is no redundancy or unnecessary detail—every word earns its place.

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?

This is a low-complexity tool with one parameter and no output schema. The description covers the action and scope, and the annotation covers idempotency and safety. It could have mentioned that it is for compute server instances (as opposed to database servers), but the tool name and sibling context make this clear. Overall, the description is complete enough for correct invocation.

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 only parameter, serverInstanceNoList, is fully described in the schema (100% coverage) as a list of server instance numbers to reboot. The main description adds no additional parameter semantics, so a 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 uses a specific verb ('Reboot') with a clear resource ('server instances') and scope ('one or more running'), distinguishing it from sibling tools like start_server, stop_server, and terminate_server. It is immediately obvious what the tool 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 phrase 'running server instances' establishes a clear context for when to use the tool (only on running instances) and indicates support for multiple instances. However, it does not explicitly mention alternatives or when-not-to-use cases, though the verb itself makes the usage clear relative to start/stop/terminate siblings.

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