Coolify: Get service

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

The readOnlyHint=true annotation already establishes that this is a safe read, so the description must add context on top of that — it does not. Nothing is said about what a service object contains, whether related resources (envs, deployments) are included, error behavior for an unknown UUID, or whether "site" scopes the lookup. The "[UNIFIED]" prefix conveys no actionable meaning.

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?

A single efficient sentence that front-loads the operation and resource. The only waste is the bracketed "[UNIFIED]" tag, which adds noise rather than information.

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 simple two-parameter read tool with no output schema, the description is thin: it leaves the mandatory "site" parameter undefined and gives no hint about the shape of the returned service details. An agent could invoke it with a UUID and still be guessing about half of the required input.

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% for both parameters, so the description carries the full burden, and it only glosses "uuid" as the service identifier. The required "site" parameter is never mentioned or explained anywhere, leaving a critical gap in an otherwise required two-param call.

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 names a specific verb and resource ("Get details of a specific Coolify service by UUID"), which cleanly separates it from lookups for applications or databases. It does not, however, explicitly contrast itself with siblings like coolify_get_application or supabase_get_service_status, so it stops short of a 5.

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 statement of when to call this versus alternatives (e.g., list vs. get, or get_service vs. get_application), and no prerequisites or exclusions. The agent must infer usage entirely from the tool name and the word "specific".

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