Delete Coolify Service

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

The description goes beyond annotations by detailing the concrete effects: 'Stops all containers and removes the service definition.' The warning highlights destructiveness, aligning well with annotations (destructiveHint: true). No contradiction with annotations.

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 extremely concise with two sentences: one stating the action and one warning. No unnecessary words, and the key verb 'Delete' is front-loaded. Every sentence adds value.

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 tool's destructive nature, the description adequately conveys the critical behavior. The schema and annotations cover most details. It could mention irreversibility or permission requirements, but overall it is complete enough for a delete operation.

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 input schema provides full coverage (100%) and adequate descriptions for all parameters. The tool description does not add additional meaning beyond the schema. With high schema coverage, the baseline score of 3 is appropriate.

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 explicitly states 'Delete a service' with a warning about stopping containers and removing the service definition. It clearly identifies the action (delete) and resource (service), distinguishing it from sibling tools like coolify_create_service or coolify_update_service.

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?

While the description does not explicitly state when to use this tool versus alternatives, the warning about destructive effects implies it is for permanent removal. The tool name and context among sibling delete tools provide sufficient clarity. A more explicit usage statement would improve this dimension.

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