Coolify: Update server

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 safety profile is covered structurally, but the description adds nothing on top: no statement of which fields a partial update touches, whether omitted fields are preserved or cleared, or what irreversible effect triggers the destructive hint. For a destructive mutation this is a notable gap.

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 wasted clauses, but this is under-specification rather than conciseness – the brevity comes at the cost of nearly all actionable information. The unexplained '[UNIFIED]' tag consumes the only available signal.

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 8 required-or-optional parameters at zero schema coverage and no output schema. Given that complexity, a one-line description is wholly inadequate; an agent cannot reliably construct a call from it.

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 8 parameters, and the description names none of them. Fields such as ip, port, user, proxy_type and the required site/uuid pair are completely undocumented, leaving the agent no way to know types, formats, or whether nulls mean 'leave unchanged'.

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 server configuration', so an agent gets the general intent. But the '[UNIFIED]' prefix is unexplained jargon, and nothing distinguishes this from the many sibling update tools touching other Coolify resources, or from coolify_create_server / coolify_delete_server beyond the verb itself.

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, no mention of alternatives such as coolify_get_server to inspect current config first or coolify_validate_server afterwards. The agent must infer that this is the mutation counterpart to the read tools purely from naming conventions.

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