Create Coolify Database

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

Annotations already indicate readOnlyHint=false (write operation). The description adds that creating a database is a write action, and mentions typical deployment context, but no additional behavioral traits like permissions, side effects, or response format.

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 two sentences, front-loaded with the purpose, and then provides supporting context and supported types. No unnecessary words or repetition.

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 12 parameters (5 required), schema coverage 100%, and no output schema, the description provides context about typical usage but lacks details on return values, error handling, or post-creation behavior (e.g., auto-deployment). It is adequate but not comprehensive.

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%, so the baseline is 3. The description does not elaborate on any specific parameter meanings beyond the schema; it only hints at typical image usage ('PostgreSQL 16'), but that is not a parameter description.

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 tool creates a new database resource, with specific verb and resource. It distinguishes from sibling tools like 'create_application' by focusing on database creation, and provides context about typical usage (PostgreSQL 16 on the same VPS for Devon's Flavor B apps).

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 gives explicit context: 'For Devon's Flavor B apps, this is typically PostgreSQL 16 deployed on the same VPS.' This guides when to use it, but does not provide when-not-to-use scenarios or compare with alternatives like update_database or list_databases.

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