Coolify: Delete service

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds useful context that volumes and Docker resources may be cleaned up, but it omits that delete_configurations also defaults to true, and gives no information on whether the deletion is reversible, required permissions, or confirmation behavior.

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, front-loaded with the action and its permanence. The unexplained "[UNIFIED]" prefix is minor noise, but otherwise there is no wasted wording.

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, non-idempotent tool with 5 undocumented parameters and no output schema, the description is too thin: it does not state that the three cleanup flags default to true, does not mention delete_configurations at all, and says nothing about the result or failure modes.

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 0%, so the description must carry the burden for 5 parameters. It only gestures at delete_volumes and docker_cleanup ("clean up volumes and Docker resources") and never mentions delete_configurations, nor does it explain the required site and uuid parameters or the fact that all three optional flags default to true.

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 ("Delete a Coolify service permanently") and signals scope with "permanently." It does not distinguish this from sibling delete tools such as coolify_delete_application or coolify_delete_database, so an agent must infer that "service" is a distinct Coolify resource type.

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?

There is no guidance on when to use this versus stopping (coolify_stop_service) or deleting a related resource, and no prerequisites or warnings about what happens to dependent resources. The word "permanently" hints at irreversibility but provides no decision criteria.

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