coolify_delete_service_scheduled_task

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

The description labels the tool as '[DESTRUCTIVE]', explicitly warning about its irreversible nature. This is helpful beyond the input schema, which includes a 'confirm' parameter for destructive operations. However, with no annotations provided, the description could further detail that deletion is permanent and not recoverable, or note that it only removes the schedule, not the service itself.

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 sentence that is clear and to the point, front-loading the destructive nature. It is short but not overly terse. Could be slightly improved by adding a note about the 'confirm' parameter requirement, but it remains efficient.

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 has 3 parameters (all documented in schema) and no output schema, the description conveys the core operation. However, it lacks context about the relationship to sibling tools (e.g., scheduling/lifecycle) and does not mention that the 'confirm' boolean is likely required for execution. A mention of the task lifecycle (e.g., 'This cannot be undone') would improve completeness.

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 already provides descriptions for all 3 parameters (uuid, confirm, task_uuid) with constraints (patterns, lengths), achieving 100% coverage. The description does not add any additional parameter-level guidance beyond what the schema offers. A baseline 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 says 'Delete a scheduled task from a Coolify service', which specifies the verb 'delete', the resource 'scheduled task', and the scope 'from a Coolify service'. It is clearly distinguished from sibling tools like 'coolify_delete_application_scheduled_task' and 'coolify_list_service_scheduled_tasks'.

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 (e.g., service vs. application scheduled tasks). It does not mention prerequisites (e.g., needing UUIDs), or when not to use it. A destructive operation like this would benefit from explicit caution or alternative tools for listing tasks first.

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