Coolify: Create database backup

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds almost nothing beyond "manual": it doesn't say what the backup touches or overwrites, whether the database must be running, whether the call is synchronous, or what permissions are needed. For a destructive mutation with no output schema, this leaves key behavioral questions unanswered.

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 with no wasted clauses, which is good, but the unexplained "[UNIFIED]" tag consumes attention and the brevity comes at the cost of under-specification rather than efficiency.

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?

This is a destructive, non-idempotent mutation with two undocumented parameters and no output schema, so the description carries the full burden of explaining behavior and targeting. It supplies neither, leaving the agent without enough information to invoke it safely and correctly.

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%, and both required parameters (site, uuid) are bare strings with no explanation in either the schema or the description. The agent must guess that uuid identifies the target database and site the Coolify instance, and gets no format or example guidance.

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 gives a specific verb and resource ("Create a manual backup of a Coolify database"), which clearly separates it from siblings like coolify_list_backup_executions or coolify_get_database_backups. It does not explicitly name those siblings or clarify scope, and the "[UNIFIED]" prefix is unexplained noise, so it falls short of a 5.

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 statement of when to use this tool versus listing or fetching backups, nor any prerequisite (e.g. database must be running) or note about scheduled vs on-demand backups. The word "manual" hints at on-demand invocation, but no alternative or exclusion is given.

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