coolify_delete_env

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

Annotations are not provided, so the description bears full burden. It marks the operation as '[DESTRUCTIVE]' but does not explain consequences (e.g., the env var is permanently removed, no undo, impact on running application). It also does not confirm whether the confirm parameter is required or what happens if omitted. No side effects are disclosed.

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, effective sentence. It front-loads the destructive nature with '[DESTRUCTIVE]', saving the agent from misinterpreting the tool as non-destructive. No wasted words.

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?

The tool is simple (3 params, no nested objects, no output schema). The description is mostly adequate given the simplicity, but it lacks confirmation about the return value (e.g., success message or error format) and does not state that env_uuid must come from a list call. For a destructive operation, more completeness would be valuable.

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 documents all parameters with descriptions. The description adds the label '[DESTRUCTIVE]' which aligns with the confirm parameter's intent, but adds no further semantics beyond the schema. 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 clearly states the action: 'Delete an environment variable from a Coolify application'. The verb 'Delete' and resource 'environment variable' are specific. It distinguishes from sibling tools like coolify_create_env, coolify_update_envs_bulk, and coolify_delete_application_storage by naming the exact resource type. However, it does not differentiate from coolify_delete_database_env or coolify_delete_service_env, which are similar delete-env tools for other contexts.

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 provide explicit guidance on when to use this tool versus alternatives like coolify_list_envs (to find env_uuid) or coolify_delete_database_env. It only implies usage for deleting env vars from applications. No prerequisites or when-not-to-use are stated.

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