create_cron_job

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

The description adds no behavioral context beyond the action. While annotations indicate readOnlyHint=false and destructiveHint=false, the description does not disclose potential side effects, whether changes require explicit apply (e.g., apply_immediately parameter), or any consequences of creating a cron job.

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, clear sentence that states the tool's purpose without filler. It is front-loaded and economical, though it provides minimal information beyond the tool name.

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's moderate complexity (8 parameters) and reliance on schema and annotations, the description alone is minimally adequate. The schema descriptions and existence of an output schema compensate for some gaps, but the description lacks usage context and behavioral nuances, making it incomplete for complex invocation scenarios.

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 coverage is 100% with all eight parameters, including apply_immediately, having descriptions. The description itself adds no parameter-level meaning, so it remains at the baseline for high schema coverage.

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 a specific verb ('Create') and resource ('cron job'), clearly stating the tool's function. It distinguishes itself from sibling tools like search_cron_jobs and delete_cron_job by indicating an additive action.

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 usage guidance is provided. The description does not mention when to use this tool versus other cron tools, nor does it state any prerequisites or alternatives. The agent must infer usage solely from the tool name and schema.

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