Coolify: Get project

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that the description offers almost nothing: it doesn't say what "details" includes, whether related resources (environments, applications) are returned, or how failures for a bad UUID surface. Given the lower bar with annotations present, this is still thin.

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 short, front-loaded sentence with no waste. The "[UNIFIED]" prefix is a tag with unclear meaning to an outside caller, but it costs almost nothing in length.

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?

There is no output schema, so the description should convey what the returned project details contain — it does not. Combined with the undefined `site` parameter and no error or scoping notes, the definition is too sparse for reliable invocation.

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%, so the description must carry parameter meaning. It clarifies only that the project is identified "by UUID", leaving the required `site` parameter entirely undefined — the agent cannot tell whether it is a Coolify instance URL, a host alias, or a region selector. This is a significant gap for a two-required-param tool.

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?

States a specific verb and resource: "Get details of a specific Coolify project by UUID". This distinguishes it from the create/update/delete project siblings and from the resource-specific getters (application, server, database). It does not explicitly differentiate itself from other project-info style tools, but the Coolify prefix and UUID targeting make the intent readable.

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?

No guidance on when to choose this versus alternatives, no prerequisites, no mention of what happens with an unknown UUID. The read-only nature is only implied by the word "Get"; the agent must infer all usage context.

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