Coolify: Stop database

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is communicated structurally. The description adds essentially nothing beyond that: it does not say whether data is preserved, whether connections are dropped, whether the stop is graceful, or how errors surface. The word "running" hints at a precondition but does not state the failure 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?

One short sentence that is front-loaded and wastes no words, which is appropriate for a simple action. Minor noise from the unresolved "[UNIFIED]" prefix, which conveys nothing to an agent.

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 mutation with no output schema and zero parameter documentation, the definition is too thin to be safely actionable. An agent cannot tell what the identifiers must be or what the consequences of the call are from this text alone.

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 coverage is 0%, so the description carries the full burden for both site and uuid, and it does neither. It never clarifies whether site is the Coolify base URL/instance or an environment, nor whether uuid identifies the database resource itself.

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 ("Stop a running Coolify database"), which is clearly distinct from siblings like restart_database, start_database, or delete_database. The one reservation is that the distinction comes mostly from the name; the description itself adds only the word "running" as scope.

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 prefer this over coolify_restart_database, coolify_delete_database, or the application/service stop variants. The only implicit condition is that the database should currently be running, and nothing says what to do if it is already stopped.

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