Coolify: Stop service

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 safety profile is covered structurally. The description adds nothing beyond that: it does not say whether in-flight requests are cut, whether configuration/data survives a stop, what happens if the service is already stopped (relevant given idempotentHint=false), or what the response looks like.

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 single sentence is front-loaded and free of padding, but it is under-specified for a destructive two-parameter operation rather than efficiently concise. The bracketed '[UNIFIED]' token consumes space without conveying usable meaning.

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 mutation with zero schema description coverage and no output schema, the definition should explain parameter meaning and side effects. Neither is present, leaving the agent to guess what 'site' means and what stopping does to the running workload.

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% for both required parameters, so the description carries the full burden of explaining 'site' and 'uuid' — and it says nothing about either. In particular 'site' is ambiguous (URL vs. identifier vs. instance) and is never clarified.

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 service'), so an agent knows the operation is a lifecycle stop on a service. It does not distinguish itself from siblings like coolify_stop_application, coolify_stop_database, or coolify_restart_service, and the '[UNIFIED]' prefix carries no decodable meaning.

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 when-to-use guidance, no statement of prerequisites (e.g., service must currently be running), and no reference to the start/restart siblings as alternatives. The agent must infer the routing decision entirely from the name.

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