deployado_create_cron_job

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

The annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=false. The description adds nothing beyond that mutation profile: it doesn't say what happens on a duplicate name, whether creation is immediately active, or what errors occur when app_id is invalid.

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 efficient sentence with no filler and the verb-resource pair is front-loaded. Its brevity is the issue in other dimensions, but this dimension is about structure and waste.

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?

This is a 6-parameter mutation tool with no output schema, yet the description never mentions return values (e.g. the new job ID), the timeout_seconds behavior, or what the cron schedule does. For a creation tool with four required parameters, this leaves agents under-informed.

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%, including a worked example for cron_expression ('0 * * * *'), so the schema carries the parameter burden. The description adds no syntax or format detail beyond what the schema already provides, which is the baseline 3 case.

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') scoped to 'an app'. It distinguishes itself implicitly from siblings such as update_cron_job, delete_cron_job, and run_cron_job, though it never names those alternatives.

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?

There is no guidance on when to use this tool instead of deployado_update_cron_job or deployado_run_cron_job. No prerequisites are stated, such as the app needing to already exist or which permissions are required.

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