coolify_run_database_storage_backup

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

No annotations are provided, so the description carries the full burden. It only states it is a write operation ('[WRITE]') but does not disclose whether the backup is synchronous, how long it might take, what resources are affected, or whether it requires specific permissions. Critical behavioral details are missing.

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 a single sentence that is concise and includes the [WRITE] prefix. It wastes no words, but it could be slightly more structured without adding length. It earns points for being efficient.

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?

Given the tool has no output schema and many sibling tools, the description should explain what an 'on-demand backup' entails, how it differs from scheduled backups, and what the agent can expect after execution. It fails to provide this context, leaving the agent underinformed.

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 100% with both parameters having descriptions ('UUID of the database', 'UUID of the storage'). The tool description adds no additional meaning beyond the schema. Baseline is 3, and the description does not improve on it.

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 ('Run an on-demand backup') and the resource ('database storage'). The [WRITE] prefix signals it's a write operation. This distinguishes it from sibling tools like 'coolify_list_database_backups' and 'coolify_create_database_backup', which involve listing or scheduling.

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?

No guidance is provided on when to use this tool versus alternatives such as 'coolify_create_database_backup' (which might set up recurring backups) or 'coolify_run_application_storage_backup'. There is no mention of prerequisites, preconditions, or when to avoid using it.

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