coolify_start_service

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

With no annotations, the description must disclose behavioral traits. It does not explain whether the service must be stopped before starting, what side effects occur, or if special permissions are required. The single word 'start' is insufficient.

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 concise at four words, but it omits critical details. While conciseness is valued, the current text under-specifies the tool's behavior, making it less useful. A slightly longer description with essential context would improve structure.

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 simple action with one parameter and no output schema, the description fails to explain the outcome of starting a service, any prerequisites, or how it differs from starting a database or application. It is incomplete for the tool's role in a larger ecosystem.

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 covers the only parameter 'uuid' with description 'Service UUID', achieving 100% coverage. The description adds no extra meaning, but the baseline is 3 given high schema coverage. No additional context about the UUID format or source is provided.

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 'Start a service' essentially restates the tool name 'coolify_start_service', adding no distinction from sibling tools like 'coolify_start_application' or 'coolify_start_database'. It fails to clarify what constitutes a 'service' in Coolify's context.

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 guidance is provided on when to use this tool versus alternatives such as 'coolify_start_application' or 'coolify_start_database'. There is no mention of preconditions, permitted states, or scenarios where starting a service is appropriate.

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