Delete Backup Execution

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

Discloses that the stored file is also deleted, adding context beyond annotations that already set destructiveHint=true. No contradictions; description aligns with annotations.

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?

Single sentence with no fluff. Front-loaded action and resource. Every word earns its place.

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?

For a simple delete tool with 5 params (all documented) and no output schema, the description covers the core action and its effect (file deletion). Lacks mention of error conditions or idempotency, but adequate given annotations.

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% and already documents all parameters. Description adds no new parameter meaning beyond stating deletion 'by UUID', which is implied by the UUID parameter names.

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?

Description uses specific verb 'Delete' and resource 'backup execution', notes deletion of stored file, and identifies by UUID. Distinguishes from sibling tools like coolify_get_backup_execution and coolify_list_backup_executions.

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 explicit guidance on when to use this tool versus alternatives like coolify_delete_database_backup. Does not mention prerequisites or destructive consequences beyond what annotations imply.

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