Coolify: Get server resources

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is lighter. It adds the scope of the result (all three resource categories) but says nothing about pagination, result size, filtering, or auth needs. Adequate under the lower bar set by annotations, but not rich.

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 front-loaded sentence with zero padding and the resource scope stated up front. The '[UNIFIED]' prefix is unexplained noise, which keeps it from a 5.

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 two-parameter read tool with no output schema, the description omits the single most important fact an agent needs: which identifier to supply. Without knowing whether 'uuid' is the server's ID or a resource ID, an agent cannot reliably invoke this tool.

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 explain both parameters, and it explains neither. 'uuid' is ambiguous — server UUID versus a resource UUID — and 'site' is entirely undefined (Coolify instance/site selector?). This is the definition's biggest gap.

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 set: 'Get all resources (applications, databases, services) deployed on a specific server.' This distinguishes it from siblings like coolify_get_server (server details) and coolify_get_application (single app). It stops short of naming those siblings explicitly, so it lands at 4 rather than 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 explicit guidance on when to choose this over coolify_get_server, coolify_get_application, or coolify_get_database. The phrase 'a specific server' weakly implies you need a server identifier, but no prerequisites, alternatives, or exclusions are given.

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