Coolify: List databases

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 to add context — but it adds none, such as whether results are scoped per site, whether pagination applies, or whether authentication is required. It essentially restates the title with no behavioral detail.

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?

The sentence is short and front-loaded, so it is not padded. However, the unexplained "[UNIFIED]" tag consumes space without conveying anything, and the extreme brevity borders on under-specification.

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?

With no output schema and a required but undocumented parameter, the description should explain the result shape and what "site" means; it does neither. For a list tool over a multi-site platform this leaves real gaps.

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 coverage is 0% for the single required parameter "site", and the description never mentions it at all. Nothing explains whether "site" is a UUID, domain, or slug, leaving the only input fully ambiguous.

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 ("List all Coolify databases"), which is enough to separate it from siblings like coolify_list_applications or coolify_list_services by resource type. The "[UNIFIED]" prefix is unexplained jargon that adds no discriminating meaning.

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 mention of prerequisites, and no reference to any alternative tool or scoping condition. The agent must infer everything from the resource name alone.

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