coolify_delete_database_backup

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

With no annotations provided, the description carries the full burden. It only labels the operation as '[DESTRUCTIVE]' and states it deletes a configuration. It does not disclose that the 'confirm' parameter must be set to true, that the default behavior does not delete S3 files unless 'delete_s3' is true, or any consequences of deletion. The transparency is insufficient for a destructive 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 a single sentence with a '[DESTRUCTIVE]' prefix, which is concise. However, it is under-specified and lacks any structure or additional context. It could be improved without losing conciseness.

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 4 parameters, is destructive, and has no output schema, the description is incomplete. It does not mention prerequisites (e.g., listing backups first), the requirement to set 'confirm' to true, or what the return value indicates. The description fails to cover key contextual information.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the parameter names and types already documented in the schema. It does not explain the role of 'confirm' or 'delete_s3' in the context of deletion.

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 resource 'scheduled backup configuration for a Coolify database'. It distinguishes from sibling tools like 'coolify_delete_backup_execution' (which deletes executions) and 'coolify_delete_database' (which deletes the database itself). The purpose is unambiguous.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that this tool deletes the configuration (not the execution) or that it requires a confirmation parameter. No exclusions or context are provided.

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