Coolify: Create environment

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the write/destructive profile is known. The description adds no behavioral context beyond restating 'create' – it does not say what an environment creation affects, whether it can be undone, or what permissions are needed. It is consistent with the annotations, not contradictory.

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?

One short, front-loaded sentence with no padding. The '[UNIFIED]' tag is non-informative noise, but the sentence itself is efficient.

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?

This is a destructive, non-idempotent mutation tool with four undocumented parameters and no output schema. The description provides only the bare minimum identity of the operation and omits parameter meaning, preconditions, and effects, leaving significant gaps for an agent to call it correctly.

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 0% and there are four parameters, so the description must compensate but largely does not. Only the phrase 'in a Coolify project' weakly maps to project_uuid; the meaning of 'site', 'name', and the optional 'description' field is left entirely undocumented.

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 and resource ('Create a new environment') within a named parent ('in a Coolify project'), which clearly separates it from coolify_get_environment. The '[UNIFIED]' prefix adds no meaning, and no sibling create tool is explicitly contrasted.

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?

There is no guidance on when to use this versus coolify_create_project or the many other create tools, nor any prerequisites such as required authorization. An agent must infer the appropriate context entirely from the name and resource noun.

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