coolify_delete_database_storage_backup

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. While it marks the tool as [DESTRUCTIVE] and mentions it deletes 'the backup schedule and archives', it doesn't disclose whether this action is irreversible, what happens to in-progress backups, whether it requires specific permissions, or what the response looks like. The 'confirm' parameter in the schema hints that confirmation is needed, but the description doesn't explain that it must be set to true to proceed. The contradiction flag is false because there are no annotations to contradict.

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, concise sentence that immediately marks the tool as destructive with a bracket prefix. It front-loads the key warning. The sentence could be slightly improved by placing the [DESTRUCTIVE] label at the very beginning before 'Delete' for even clearer emphasis, and by adding a brief note about confirmation, but overall it's 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 that parameters are fully covered in the schema, no output schema exists, and the tool is destructive, the description provides adequate but not comprehensive detail. It names the two deleted components (schedule and archives) and warns of destruction, but lacks behavioral context (irreversibility, prerequisites) and usage guidelines. For a destructive operation, more guidance is warranted.

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%, so the schema already describes all three parameters ('uuid', 'confirm', 'storage_uuid'). The description adds no additional semantic information beyond what's in the schema – it doesn't explain how the uuid and storage_uuid relate (e.g., that uuid is the database's UUID and storage_uuid is the storage's UUID, and both are needed to identify a specific backup schedule). It also doesn't clarify that 'confirm' must be true for the operation to succeed. Baseline 3 is appropriate given full schema coverage.

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 verb 'Delete' and the specific resource: 'backup schedule and archives for a database storage'. This distinguishes it from siblings like 'coolify_delete_database_backup' (which likely deletes only a backup execution result) and 'coolify_delete_application_storage_backup'. However, it could be more precise by explicitly noting that this refers to the entire backup schedule, not just a single backup.

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 gives some context by labeling it [DESTRUCTIVE], implying it should be used with caution, but it provides no explicit when-to-use or when-not-to-use guidance. There's no mention of alternatives or prerequisites (e.g., that the database and storage must exist). The sibling tools list suggests there are other backup-related tools (like 'coolify_set_database_storage_backup', 'coolify_run_database_storage_backup', 'coolify_delete_database_backup'), but the description doesn't help the agent choose among them.

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