coolify_update_scheduled_task

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

Annotations already declare it as non-read-only, idempotent, and non-destructive. The description adds that the tool is subject to operation mode, allowlist, and production guard policies, which is useful context beyond the annotations, but it does not explain consequences or response behavior.

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?

Two short sentences with no redundancy. The policy caveat is concise, and every word earns its place.

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?

With 10 parameters, no output schema, and only a terse policy reference, the description is too minimal to fully support an agent. It doesn't explain update behavior, what fields are updated together, or how the policies might block or alter the call.

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 provides full descriptions for all 10 parameters, so the baseline is 3. The description does not add parameter-specific details beyond the schema, though the production guard mention loosely relates to environment_name.

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 uses the specific verb 'Update' with the resource 'scheduled task', clearly distinguishing it from sibling tools like coolify_create_scheduled_task and coolify_execute_scheduled_task. The core purpose is explicit and unambiguous.

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 on when to use this tool versus coolify_create_scheduled_task or other update tools. The policy caveat provides a constraint but does not help select among alternatives.

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