Reinstall server

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

No annotations are provided, so the description carries the full burden. It does disclose the critical destructive trait ('can wipe server files'), which is the single most important fact. But it omits whether data is recoverable, what a reinstall actually does to the container/OS, and what gets returned.

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?

Two short sentences with the action stated first and the danger warning second. Efficient, though 'use with care' is a soft filler phrase that could be replaced with concrete consequences.

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 destructive mutation tool with no annotations and no output schema, the description covers the key risk but leaves gaps: irreversibility, scope of what is wiped, and whether configuration/startup variables survive. Adequate but not 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?

Schema coverage is 80% and the panel/API-key overrides are documented in the schema. The description adds nothing about the required 'server' parameter or the credential overrides, so baseline 3 applies.

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?

States a specific verb and resource: 'Trigger a server reinstall.' Clear and distinct from siblings like server_power or server_rename, though it never explicitly contrasts itself with them.

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?

'use with care' is a warning, not guidance. It says nothing about when a reinstall is appropriate versus alternatives such as server_power (restart) or backup_restore, nor about prerequisites or required permissions.

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