Coolify: Update service env

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it doesn't say what an update overwrites, whether the previous value is recoverable, what the is_preview or allow_compose_environment_override flags do, or whether a redeploy is triggered.

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 sentence is not padded, but '[UNIFIED]' is unexplained noise and the sentence is so compressed that it communicates almost nothing. Brevity here comes at the cost of usefulness rather than from efficiency.

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 with six parameters at zero schema coverage and no output schema. The description supplies none of the missing context: no preconditions, no effect of overwriting, no scoping detail for site/uuid. It is not adequate for the tool's complexity.

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% across six parameters, so the description must compensate and does not. It never explains key/value pairing, what 'site' and 'uuid' identify, or the meaning of is_preview and allow_compose_environment_override, which are the two parameters an agent is most likely to misuse.

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 ('Update an environment variable for a Coolify service'), which is enough to distinguish it from the create/delete env siblings. It does not distinguish it from coolify_update_service_envs_bulk or coolify_update_application_env, and the '[UNIFIED]' prefix carries no meaning for an agent.

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 when-to-use guidance, no mention of the bulk sibling for multi-variable edits, and no note about the application-env equivalent. The agent must infer everything about tool selection from the name alone.

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