coolify_delete_server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly labels the tool as '[DESTRUCTIVE]' and states it will 'permanently delete a server' and 'stop all its resources'. This is exceptional clarity about the irreversible, destructive nature of the operation.

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, concise sentence that efficiently communicates the destructive action. The '[DESTRUCTIVE]' prefix immediately signals the tool's nature. However, it could be slightly more structured by separating the warning from the action description.

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?

Given the tool's simplicity (three parameters, no output schema, no nested objects), the description is largely complete. It covers the core purpose, destructive nature, and resource impact. It could be enhanced by briefly mentioning the need for the 'confirm' parameter to prevent accidental deletion.

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 description coverage is 100%, so the schema already documents all three parameters (uuid, force, confirm). The description adds no further meaning to these parameters beyond what is in the schema. Baseline 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 clearly states the verb 'delete' and the resource 'server', and adds the important nuance that it 'stop[s] all its resources'. This differentiates it from sibling tools like 'coolify_delete_application' or 'coolify_delete_database' which delete specific resources, not the server itself.

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 does not provide any guidance on when to use this tool versus alternatives. For example, it doesn't mention that to simply stop a server without deleting, one should use 'coolify_stop_server' (which doesn't exist in siblings, but the intent is missing). There is no clarification on prerequisites (e.g., need to stop resources first) or when to use the 'force' parameter.

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