coolify_create_service

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

No annotations provided, so the description must fully disclose behavioral traits. It states '[WRITE]' and 'one-click Docker Compose service', hinting at creation behavior, but lacks details on idempotency, validation steps, required permissions, or return value (no output schema). With zero annotation coverage and minimal description, the agent has insufficient context to anticipate side effects.

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?

At one short sentence, the description is concise with no wasted words. However, it could be slightly more informative without sacrificing brevity, e.g., by mentioning required resources (server, project) or that the service type must be one of the supported Docker Compose services. The '[WRITE]' tag is a helpful structural hint.

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 8 parameters (4 required), a nested 'custom_fields' object, no output schema, and dozens of sibling tools, the description is too minimal. It doesn't explain what constitutes a 'service' vs. an 'application' or 'database', what the consequence of 'instant_deploy' is, or how to obtain valid UUIDs for server, project, and environment. The agent lacks enough context to reliably invoke this tool.

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 baseline is 3. The description adds 'one-click Docker Compose service' context but does not elaborate on parameter semantics beyond what the schema already provides. For example, it doesn't clarify how 'custom_fields' or 'instant_deploy' interact with the overall creation flow. Coverage is high, so no penalty, but the description doesn't add significant value.

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?

Description clearly states the verb 'Create' and resource 'Coolify service', and specifies it's a 'one-click Docker Compose service', which distinguishes it from sibling tools like coolify_create_application or coolify_create_database. The prefix '[WRITE]' further clarifies the operation type.

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 vs. alternatives (e.g., coolify_create_application for custom apps). The description implies usage for pre-packaged Docker Compose services, but does not explain which service types are valid or when to use this instead of coolify_update_service. No exclusions or prerequisites mentioned.

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