coolify_update_service_scheduled_task

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. However, it only states '[WRITE]' and 'Update a scheduled task', which implies mutation but does not detail side effects, authorization needs, idempotency, or what happens if the task does not exist. The '[WRITE]' tag is a weak substitute for proper behavioral annotation.

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 line, which is short, but it lacks essential structure for a tool with 8 parameters. The '[WRITE]' prefix is useful, but the main text does not fully capture the tool's purpose or behavior. It is not excessively long, but it is under-specified given the tool's complexity.

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 high parameter count (8) and the absence of annotations or an output schema, the description is insufficient. It does not explain return values, error conditions, or the expected behavior when partially updating fields. The presence of sibling tools for create and delete further demands clear differentiation that the description fails to provide.

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%, providing a baseline of 3, but the description adds no value beyond the schema—it merely repeats 'Update a scheduled task' without explaining parameter relationships or usage context. For a tool with 8 parameters, the description should clarify how parameters like 'name', 'command', 'frequency', and 'enabled' relate to updating a scheduled task, which is missing.

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 states the verb 'Update' and the resource 'scheduled task for a Coolify service', with the '[WRITE]' prefix clearly indicating write semantics. It distinguishes from sibling tools like 'coolify_create_application_scheduled_task' and 'coolify_delete_application_scheduled_task' by focusing on update, but could be more specific about which aspects of the task can be updated beyond the schema parameters.

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 explicit guidance is provided on when to use this tool versus its siblings (create or delete scheduled tasks). The description does not mention prerequisites, such as requiring the service UUID and task UUID, nor does it differentiate from other update operations like 'coolify_update_application_scheduled_task' for applications.

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