coolify_delete_service

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

The description includes the [DESTRUCTIVE] tag in the text, highlighting irreversible behavior. It also lists parameters like 'delete_volumes' and 'docker_cleanup' that indicate cascading side effects. Since no annotations are provided, the description carries the full burden and does a moderate job disclosing these behaviors, but it could explicitly state that the service, its data, and Docker resources may be permanently removed.

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 conveys the core purpose and danger (DESTRUCTIVE). It is front-loaded with the key warning and avoids unnecessary verbiage. It could briefly note the need for confirmation for completeness.

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 lack of output schema and annotations, the description is adequate but not thorough. It provides a basic understanding of the destructive nature and references the confirm parameter implicitly, but does not explain the return value (e.g., success status, deleted resource details) or warn about irreversible side effects like volume and Docker cleanup in more specific terms. For a 4-parameter tool with no output schema, more detail would be helpful.

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 already provides descriptions for all four parameters (100% coverage), so the description need not repeat them. The description adds minimal semantics beyond the schema–it implies destruction but does not explain the role of each parameter in the deletion process or how they affect the outcome.

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 action ('Permanently delete') and the resource ('Coolify service'), which distinguishes it from application- and database-specific delete tools in the sibling list. However, it does not explicitly call out that it targets a 'service' resource specifically, relying on the tool name for that distinction.

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 marks the operation as [DESTRUCTIVE] and requires a 'confirm' parameter, implying a safety check before performing the deletion. However, it provides no explicit guidance on when to use this tool versus alternatives like 'coolify_delete_application' or 'coolify_delete_environment', nor does it mention prerequisites (e.g., stopping the service first or checking for related resources).

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