Coolify: Delete database

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the danger profile is structured data. The description does add something beyond that: it emphasizes permanence and discloses that volume and Docker resource cleanup are part of the operation's scope, which matters for blast radius. However, it never states that all three cleanup flags default to true (so a default call is maximally destructive) and gives no warning about irreversibility or auth requirements.

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 resource, with no padding. The only blemish is the unexplained "[UNIFIED]" prefix, which occupies prime attention space without telling the agent anything.

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 permanent, destructive operation with five parameters at 0% schema description coverage and no output schema, the description is too thin. It omits one of the three behavior-altering flags, never discloses their true-by-default values, and says nothing about what the caller gets back or how failure looks.

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 parameter burden and it largely does not. "Clean up volumes and Docker resources" loosely maps to delete_volumes and docker_cleanup, but delete_configurations is entirely unmentioned, the defaults (all true) are never stated, and the required site/uuid parameters are never explained.

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 states a specific verb and resource ("Delete a Coolify database permanently") and its target is unambiguous against siblings like coolify_get_database, coolify_restart_database or coolify_update_database. The "[UNIFIED]" prefix is unexplained noise that adds no discriminating information, but the core purpose statement is clear.

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 choose this deletion tool versus related lifecycle operations, and no statement of prerequisites, permissions, or whether confirmation/irreversibility checks are expected from the caller. The only usage-adjacent content is "Optionally clean up volumes and Docker resources," which describes options rather than when to use the tool.

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