coolify_create_service

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

No annotations are provided, so the description must carry the full burden. It adds minimal behavioral context (can create from template or docker-compose). It does not disclose side effects, authentication needs, or whether the service is deployed automatically (though 'instant_deploy' parameter hints at it).

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 concise sentence with no wasted words. It front-loads the core action. Could be more detailed, but it is appropriately sized for a straightforward tool.

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 complexity of a creation tool with 8 parameters and no output schema, the description is insufficient. It does not mention prerequisites (e.g., project and server must exist), return values, or further behavior. The agent lacks information to use the tool effectively.

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 coverage is 100%, so parameters are already documented. The description adds some value by framing the two creation modes ('template' vs 'docker-compose'), which maps to 'type' and 'docker_compose_raw'. However, it doesn't add significant meaning beyond what the schema provides.

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 ('Create a new service') and the resource ('service'), and mentions two modes ('from template or docker-compose'). It distinguishes from sibling tools like coolify_create_service_env, but doesn't explicitly differentiate from other creation tools like coolify_create_application_public.

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 provides no guidance on when to use this tool versus alternatives, nor does it specify prerequisites or context for using the template vs docker-compose approach. No usage scenarios or exclusions are mentioned.

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