coolify_delete_environment

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

No annotations are provided, so the description carries full burden. It explicitly marks the tool as [DESTRUCTIVE] and requires environment emptiness, but does not disclose other behaviors like whether the operation is irreversible, if it affects dependent resources, or any permission/authorization requirements.

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 that is direct and front-loaded with key information: it states the destructive nature, the resource type, the target, and the precondition. 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?

Given the tool is destructive and has 3 parameters (including a confirm flag), the description should explain when to set confirm, potential return values, or error states (e.g., what happens if the environment is not empty). Without an output schema, the description must compensate but does not. It is underspecified for safe usage.

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 baseline is 3. The description adds no additional meaning beyond the schema; for example, it does not explain the difference between environment_name and environment_uuid, nor that 'confirm' is required for destruction. The description adds no parameter-specific context.

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 it deletes an environment from a Coolify project, with a clear precondition ('must be empty'). The name 'coolify_delete_environment' is descriptive and distinct from siblings like 'coolify_delete_project' and 'coolify_delete_application'.

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 provides a precondition ('environment must be empty') but does not guide when to use this tool vs. alternatives like updating an environment or listing environments first to verify emptiness. No when-not-to-use guidance.

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