Coolify: Restart service

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, so the safety profile is known from structured data. The description adds nothing beyond that: it does not mention downtime, in-flight request disruption, whether the restart is immediate or queued, or whether a failed restart leaves the service stopped.

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?

It is a single front-loaded sentence with no filler, which is good, but the "[UNIFIED]" tag conveys no meaning and consumes part of an already minimal description. Brevity here reads as under-specification rather than precision.

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 two undocumented required parameters and no output schema, the description should carry far more weight. An agent has no information on parameter meaning, expected effects, or failure behavior before invoking an operation that can take a service offline.

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 neither "site" nor "uuid" is documented anywhere, and the description does not compensate. It does not explain what "site" refers to (a Coolify instance or a project) or whether "uuid" is the service, application, or environment identifier.

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 names a specific verb and resource ("Restart a Coolify service"), so the basic operation is identifiable. However, the "[UNIFIED]" prefix is unexplained jargon, and the wording gives no way to tell this apart from siblings like coolify_restart_application or coolify_restart_database that restart more specific resource types.

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 tool versus the resource-specific restart siblings, and no stated prerequisites (e.g., whether the service must be running, whether the deployment must be healthy). An agent must guess from the name alone.

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