coolify_create_database_storage

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

No annotations are provided, so the description carries the full burden. While the '[WRITE]' tag and verb 'Add' imply modification, the description does not disclose behavioral details like permissions required, whether the operation is reversible, or side effects on existing storage mounts. This leaves significant gaps for a write operation.

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, clear sentence that front-loads the purpose. However, given the complexity of 8 parameters and the context of write operations, the description could be slightly more structured to include critical usage notes 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?

With 8 parameters, no annotations, no output schema, and the need to distinguish between persistent and file storage types, the single-sentence description is insufficient. It does not explain conditional parameter dependencies (e.g., 'content' for file, 'fs_path' for directory) or return behavior, leaving the agent under-informed for correct invocation.

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 schema description coverage is 100%, with clear descriptions for each parameter (e.g., 'Volume name (required for persistent storages)', 'Storage type: persistent volume or file mount'). However, the description does not add further meaning beyond what the schema provides. Since baseline is 3 for high coverage, this is adequate.

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 ('Add') and the resource ('a persistent or file storage mount to a Coolify database'). It distinguishes this from sibling tools like 'coolify_list_database_storages' and 'coolify_delete_database_storage' by focusing on creation. The '[WRITE]' tag further indicates it is a write operation.

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 does not specify when to use this tool versus alternatives, such as when to create a persistent volume versus a file mount, or prerequisites like ensuring the database exists. It also does not mention exclusions or related tools for managing storage.

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