list_coolify_databases

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

With no annotations and a description that only states 'Execute', there is no disclosure of behavioral traits such as read-only nature, authentication requirements, or potential side effects. The AI agent has no information about the tool's safety or expected behavior.

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 very concise but adds no value, essentially repeating the tool name. It is under-specification rather than effective conciseness, as it fails to provide any useful information in its single sentence.

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?

Given the simplicity of the tool (no parameters), the description is still incomplete. It does not mention what the tool returns (e.g., a list of databases) or any context such as that it requires no arguments. The presence of many sibling list tools makes this omission more significant.

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 tool has zero parameters and the input schema coverage is 100% (trivially). With 0 parameters, the baseline is 4, and the description, while minimal, does not need to add parameter-level meaning. However, it could still benefit from context about the lack of parameters.

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 'Execute list_coolify_databases' is essentially a tautology of the tool name, providing no additional clarity. It fails to specify that the tool lists databases from Coolify or to distinguish it from sibling list tools like list_coolify_applications.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives such as list_coolify_applications or list_coolify_services, which are similar list operations.

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