Restart Server

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the description's 'DESTRUCTIVE.' adds no new behavioral information. It does not explain what is affected beyond 'restart'—for example, active requests, sessions, or queued tasks—so the agent still lacks consequence-level detail.

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 compact and front-loaded, with the endpoint embedded efficiently. The all-caps 'DESTRUCTIVE.' is slightly redundant with the destructiveHint annotation, but it does not make the description bloated.

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?

For a zero-parameter restart endpoint, the description is minimally viable: it names the operation and flags it as destructive. However, it omits practical consequences such as temporary unavailability, loss of in-progress work, or whether any state persists across the restart.

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 has zero parameters, so there is nothing for the description to clarify. This matches the baseline for a no-parameter tool.

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 states a specific verb ('Restart') and resource ('the SD.Next server'), includes the exact endpoint, and is clearly distinct from sibling operations like shutdown, interrupt, or checkpoint refresh.

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 gives no guidance on when to use restart versus alternatives such as sdnext_shutdown, sdnext_refresh_checkpoints, or sdnext_unload_checkpoint. It also does not mention prerequisites or situations where restart is appropriate.

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