coolify_create_application_scheduled_task

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

No annotations are provided, so the description must fully disclose behavioral traits. It only indicates it is a write operation via '[WRITE]' and 'Create'. Missing details: idempotency, side effects, error behavior, or what happens on duplicate names or invalid inputs.

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 at one sentence. While efficient, it lacks structure like front-loading key context (e.g., mutation type). It earns its place but could benefit from slight expansion.

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 a tool with 7 parameters (4 required) and no output schema or annotations, the description is incomplete. It does not explain return values, prerequisites (e.g., application must exist), or validation details for parameters like 'frequency' or 'timeout'. Significant gaps remain.

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 the input schema already documents each parameter (e.g., 'name', 'frequency'). The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the description does not compensate for any gaps.

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 clearly states the tool is for creating a scheduled task for a Coolify application. It includes a '[WRITE]' hint for mutation type and the verb 'Create' along with the resource 'scheduled task'. It distinguishes from sibling tools like 'coolify_create_service_scheduled_task' by specifying 'application'.

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 tool vs alternatives (e.g., updating or deleting scheduled tasks, or creating service scheduled tasks). No prerequisites or conditions are mentioned, leaving the agent to infer usage context entirely from the tool name.

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