delete_server

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

While the description warns of destructiveness ('DESTRUCTIVE', 'permanently delete'), it lacks detail on what exactly happens to associated data (backups, files, logs) and any safety mechanisms. With no annotations, the description carries full burden and is insufficient.

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?

Very concise: a single sentence with a clear warning prefix ('DESTRUCTIVE') and direct statement of action. No unnecessary words.

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 tool with no output schema and minimal description, it lacks important context such as whether deletion is reversible, impact on other resources, and post-deletion state. The description is too sparse to fully inform the agent.

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 'serverId' has no description in the schema (0% coverage). The tool description does not provide any additional meaning, format, or examples for the parameter.

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?

Description clearly states the action ('permanently delete') and the resource ('a server and all its data'). It distinguishes from sibling tools like stop_server, restart_server, and remove_mod.

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 on when to use this tool versus alternatives, no prerequisites or conditions (e.g., server must be stopped), and no mention of caution or confirmation needed.

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