coolify_delete_service_env

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

With no annotations, the description carries full burden for behavioral disclosure. It includes the label '[DESTRUCTIVE]' and the schema has a 'confirm' parameter, both hinting at destructiveness. However, it does not explain side effects (e.g., whether deletion triggers a redeploy), permanence, or auth requirements. The label provides some transparency but lacks completeness.

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 clear action and a useful '[DESTRUCTIVE]' prefix. There is no redundant information, and every word contributes to understanding. It is ideally concise.

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 destructive operation with no output schema and no annotations, the description is too sparse. It does not explain what happens after deletion, how to confirm, what the response looks like, or how the two required UUIDs relate to each other. The presence of the 'confirm' parameter is a key usage detail that the description omits.

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% (all parameters have descriptions), so baseline is 3. The tool description adds no extra meaning beyond what the schema already provides (e.g., it does not explain how to obtain the UUIDs or the role of 'confirm'). The schema is self-sufficient, so the description does not degrade but also does not enhance.

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 states a specific verb ('Delete') and resource ('environment variable from a Coolify service'), making the core purpose clear. However, it does not differentiate this tool from sibling tools like 'coolify_delete_env' or 'coolify_delete_database_env', which have overlapping functionality.

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 guidance is provided on when to use this tool versus alternatives (e.g., coolify_delete_env for applications, coolify_delete_database_env for databases). Prerequisites (e.g., having the service UUID and env_uuid) are not mentioned, and no when-not-to-use conditions are given.

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