Create Scheduled Task

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

Annotations already declare readOnlyHint=false (write operation), openWorldHint=true, and idempotentHint=false. The description 'Add a cron task' confirms mutation but adds no further behavioral context (e.g., permissions, side effects, audit). No contradiction with annotations.

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 of 8 words, highly concise and front-loaded. However, the extreme brevity sacrifices context that could be included without significant bloat.

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?

Despite the tool having 9 parameters and no output schema, the description provides minimal context. It does not explain the return value, behavior on failure, or how scheduled tasks integrate with the Coolify system. A more complete description would aid the agent in using the tool correctly.

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?

Input schema covers all 9 parameters with descriptions (100% coverage). The tool description does not add extra meaning beyond the schema. Although the 'instance' parameter description includes safety guidance, that is part of schema, not the main description.

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 'Add a cron task to an application or service' clearly states the verb ('Add') and the resource ('cron task') and specifies the target ('application or service'). It distinguishes the tool from sibling tools like delete_scheduled_task and update_scheduled_task.

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., update_scheduled_task). There is no mention of prerequisites or scenario-based recommendations. The use is implied but not elaborated.

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