coolify_delete_application_storage

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

No annotations are provided, so the description must carry full burden. It marks the operation as '[DESTRUCTIVE]', which adds transparency about irreversibility. However, it does not disclose any other behavioral traits such as required permissions, side effects on the application, whether it warns or requires a confirm parameter (though schema has 'confirm' boolean), or potential impact on running applications.

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, clear sentence with the destructive flag front-loaded. Every word serves a purpose with no redundancy. Ideal length for a delete operation.

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 there is no output schema and no annotations, the description could be improved by explaining what happens after deletion (e.g., storage is removed immediately, application may need restart). For a destructive operation with 3 parameters, the description is minimally adequate but lacks completeness regarding effects and confirmation flow.

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 the three parameters ('uuid', 'storage_uuid', 'confirm') are already well-documented in the schema with types, patterns, and descriptions. The description adds no additional semantics beyond what the schema provides. Baseline 3 is appropriate.

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 explicitly states the action ('Remove'), the target resource ('persistent or file storage mount'), and the subject ('Coolify application'). It distinguishes clearly from sibling tools like 'coolify_delete_database_storage' by specifying 'application storage'.

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 does not specify when to use this tool versus alternatives (e.g., updating storage, or deleting database/service storage). However, the tool name and context provide implied guidance since it is the only delete for application storage among siblings. No when-not-to-use or prerequisites are mentioned.

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