list_databases

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

The word 'List' clearly signals a read-only enumerative operation, and 'all databases in Coolify' defines the scope. However, with no annotations available, the description does not disclose pagination behavior, return format, or any access requirements. This is minimal but acceptable for a straightforward listing tool.

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 description is a single, front-loaded sentence containing only the essential information: the verb, the resource, and the scope. Every word earns its place with no redundancy.

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 zero-parameter tool with no output schema, 'List all databases in Coolify' is almost fully sufficient for correct invocation. It does not describe the response shape or note whether results are paginated, but the listing purpose is clear enough for an agent to call it appropriately.

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?

The input schema has zero parameters and 100% schema description coverage, so there is nothing for the description to add. The 0-parameter baseline of 4 applies.

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 the verb 'List' and the resource 'all databases in Coolify', making the tool's purpose clear and distinct from sibling list tools like list_applications and list_servers. It does not explicitly contrast with those siblings, but the resource name is enough to disambiguate.

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?

The description implies this tool is used when one needs to enumerate all databases, but it offers no explicit guidance on when to prefer it over create_database or other sibling tools. For such a simple zero-parameter tool, the intended usage is reasonably inferable, though not stated.

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