coolify_delete_application

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

No annotations are provided, so the description carries full burden. It clearly states the action is permanent and destructive with '[DESTRUCTIVE]' and 'Permanently', which is good. However, it does not disclose side effects like whether the deletion is irreversible, what happens to associated resources (e.g., if delete_volumes and docker_cleanup are false), or whether it requires confirmation via the 'confirm' parameter. The description partially compensates for missing 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?

The description is a single, front-loaded sentence with zero wasted words. The '[DESTRUCTIVE]' tag immediately conveys critical behavioral context, and 'Permanently delete a Coolify application' is precise and complete.

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 destructive nature and no output schema, the description does not explain what the return value is (e.g., success message or ID). However, the schema covers all parameters well, and the description clearly sets expectations for the operation's finality. A note about the confirmation parameter or return behavior would increase completeness, but it is adequate for a deletion tool with well-documented params.

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 schema already documents all four parameters with descriptions. The tool's description adds no additional parameter meaning beyond the schema's structured definitions. Baseline 3 is appropriate since the schema does the heavy lifting.

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 uses a clear, specific verb ('delete') and resource ('Coolify application'), immediately stating the action's permanent nature with the '[DESTRUCTIVE]' prefix. This clearly distinguishes it from siblings like 'coolify_stop_application' (temporary halt) and 'coolify_delete_application_storage' (storage deletion only).

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 explicitly signals the destructive nature and permanence of the operation via '[DESTRUCTIVE]' and 'Permanently delete'. This implies careful consideration before use, though it does not explicitly state when not to use it (e.g., use 'coolify_stop_application' instead) or list any prerequisites (e.g., application must exist). The sibling list contains safer alternatives.

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