coolify_update_service_scheduled_task

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

With no annotations, the description carries the full burden, yet beyond the '[WRITE]' tag it discloses nothing: no partial-vs-full update semantics, no permission requirements, no effect on running executions, no irreversibility notes. For a mutation tool with 8 parameters this is a substantial gap.

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?

A single short sentence with no padding, and the crucial '[WRITE]' marker is front-loaded. It is efficient but borders on under-specified rather than optimally informative.

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 an 8-parameter mutation with no annotations and no output schema, the description says almost nothing an agent couldn't get from the tool name and schema. It omits update semantics, side effects, and sibling routing, leaving real gaps.

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 every parameter (uuid, task_uuid, name, command, frequency, timeout, container, enabled) is documented in the schema itself. The description adds no extra meaning, which is the baseline 3 case.

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?

States a specific verb (update) and resource (scheduled task for a Coolify service), and the '[WRITE]' tag flags the mutation. It distinguishes from the application-level sibling by naming 'service', though it doesn't call out coolify_update_application_scheduled_task explicitly.

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 on when to use this versus coolify_create_service_scheduled_task or coolify_delete_service_scheduled_task, and no prerequisites such as needing an existing task_uuid. Usage must be inferred entirely from the name.

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