Shutdown Server

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

Annotations already declare destructiveHint=true, so the description's 'DESTRUCTIVE' label mostly repeats structured data. It adds the endpoint and names the action, but it does not disclose consequences like in-progress task loss or whether the process can be restarted. It aligns with annotations, so no contradiction.

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 sentence plus a warning, with the action and endpoint front-loaded. Every word earns its place, and the 'DESTRUCTIVE' emphasis is direct and useful.

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 simple, zero-parameter shutdown tool, the description adequately identifies the action, endpoint, and destructive nature. It could be slightly richer by noting the effect on running jobs, but the annotations and simplicity of the tool keep it reasonably complete.

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 tool has zero parameters and the schema fully covers them, so the description does not need to explain parameter meaning. The baseline for no-parameter tools is 4, and there is nothing missing in that area.

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 ('Shut down') and a specific resource ('the SD.Next server'), and it pinpoints the exact API endpoint. This clearly distinguishes it from sibling operations like sdnext_restart.

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 implies the tool is used when the server needs to be stopped, but it does not explicitly say when to prefer this over alternatives such as sdnext_restart. The 'DESTRUCTIVE' warning adds caution but not direct usage guidance.

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