coolify_create_service

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

The description adds the requirement of safe-write operation mode, which is behavioral context beyond the annotations. However, it does not disclose other potential side effects, permissions, or response behavior. Annotations already indicate a write operation, so the extra value is limited but present.

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 short sentences with no superfluous content. It front-loads the primary purpose and adds the key requirement, making it highly concise and well-structured.

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?

For a creation tool, the description is minimally adequate but lacks details on return values, workflow after creation, or potential side effects. The schema and annotations cover parameter meanings and the write nature, but the description alone would leave some gaps for an agent handling complex scenarios.

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 input schema already documents all parameters. The description adds no additional parameter-level meaning, matching the baseline of 3 for high schema coverage.

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 service in a project environment, using a specific verb ('create') and resource ('service'). It distinguishes from sibling tools like coolify_create_application and coolify_create_database by focusing on services.

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 useful context by noting that safe-write operation mode is required, which tells the agent when the tool can be invoked. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to infer appropriate use.

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