coolify_create_database_backup

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'Create a backup' without revealing whether the operation is synchronous, whether it triggers a background job, what permissions are needed, or what the return value is. This is severely insufficient for a write operation.

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 description is extremely concise—a single sentence with no redundant words. Every word serves a purpose, and the '[WRITE]' prefix provides a quick action hint. No improvement is needed in terms of brevity.

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?

Although the tool has only one parameter and no output schema, the description fails to provide essential context such as the nature of the backup (e.g., immediate vs. scheduled), the expected response, or how it differs from other backup creation tools like 'coolify_run_database_storage_backup'. The description is too minimal to be fully helpful.

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?

The input schema has 100% coverage with a clear description for the 'uuid' parameter. The description adds no additional meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 clearly states the action ('Create a backup') and the resource ('a Coolify database'). It uses a specific verb+resource pattern and, given the sibling tools, it distinguishes itself from related backup tools like 'coolify_list_database_backups' and 'coolify_set_database_storage_backup' by focusing on creating a backup of a database entity.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'coolify_set_database_storage_backup' or 'coolify_run_database_storage_backup'. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage 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.