Coolify: Update service

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered; the description adds nothing beyond it. It never warns that replacing docker_compose_raw could overwrite a live service definition, nor does it state whether omitted fields are preserved or cleared.

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?

It is a single short sentence with no padding, which is structurally clean. However, the brevity comes at the cost of substance, and the bracketed "[UNIFIED]" prefix is unexplained noise rather than useful framing.

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, non-idempotent mutation with five undocumented parameters and no output schema, the description supplies essentially none of the context an agent needs to call it safely. There is no mention of scope of change, reversibility, or what the response confirms.

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% with five parameters, so the description must carry the explanatory load and it does not. It gives no meaning for site or uuid, and no guidance on the null-defaulted name/description/docker_compose_raw beyond the loose word "settings."

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 a Coolify service settings"), so an agent knows it mutates a service. But "settings" is vague and it does not distinguish this from the many sibling update tools (coolify_update_service_env, coolify_update_application, coolify_update_server) or clarify what a "service" is in Coolify terms.

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 prerequisites, and no pointer to alternatives such as coolify_update_service_env for environment variables or the create/delete siblings. The unexplained "[UNIFIED]" tag hints at a broader endpoint but conveys nothing actionable.

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