coolify_list_database_storages

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

No annotations are provided, so the description carries full burden. It only states 'list', implying a read operation, but does not disclose any behavioral traits such as permission requirements, pagination, rate limits, or what happens if the database does not exist. The description adds minimal value beyond the verb.

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 sentence of 10 words, which is concise but lacks substance. Every word earns its place, but the brevity sacrifices useful information. It could be expanded slightly to improve clarity without being verbose.

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 lack of an output schema, the description does not hint at what the response contains (e.g., fields like name, mount path, size). No annotations are provided. For a simple list tool, the description is incomplete; the agent would need to infer or inspect the API to understand the return value.

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 100% (the 'uuid' parameter is fully described in the schema). The description does not add any additional meaning or context about the parameter beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states the action (list) and the resource (persistent and file storages for a Coolify database). It distinguishes this tool from siblings like 'coolify_list_databases' (which lists databases) and 'coolify_list_database_backups' (which lists backups) by specifying 'storages'.

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 explicit guidance on when to use this tool versus alternatives such as 'coolify_list_application_storages' or 'coolify_list_service_storages'. The context of database-specific storage is implied but not stated as a selection criterion. No when-not-to-use examples are provided.

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