create_cron

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'Create a new cron task' and gives parameter requirements, but does not disclose side effects, whether the cron starts immediately, permission requirements, or return behavior. This is a significant gap for a mutation tool.

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 two sentences with a clear verb-first structure. It wastes no words and front-loads the main purpose, while effectively embedding examples.

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 tool has 7 parameters and no output schema or annotations, the description is somewhat minimal. It only addresses the two required parameters and gives no guidance on optional parameters, creation behavior, or possible errors. For a moderately complex create operation, this feels incomplete but not severely inadequate.

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 already covers all 7 parameters with descriptions, giving a baseline of 3. The description adds value by providing concrete examples for command (`ql task xxx.js`) and schedule (`0 8 * * *`), reinforcing the required format and clarifying that command can be any shell command.

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 'Create a new cron task' with a specific verb and resource, distinguishing it from sibling tools like update_cron and delete_crons. It also specifies the required inputs with examples, making its purpose 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?

The description explicitly states that command and schedule are required, giving clear conditions for using this tool. It does not mention alternatives or exclusions, but the context is clear enough for a creation tool among siblings like list_crons and update_cron.

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