Create Agency Cron Job

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a cron job.' only states the action, with no mention of the agency scope, effects on the website, required permissions, or return values. This is a significant gap for a creation operation.

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 concise sentence, which is front-loaded and efficient. However, it is so brief that it borders on under-specification, providing only slightly more information than the tool name itself. It is not bloated, but also not appropriately detailed.

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 lack of annotations and output schema, the description should offer more context. It fails to explain what makes this tool 'agency-specific', how it relates to website_uid, or any behavioral implications (e.g., schedule format, execution details). This makes the tool difficult to invoke correctly without additional documentation.

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 input schema has 100% parameter description coverage (command, schedule, website_uid), so the schema already documents parameters effectively. The description itself adds no additional semantic context beyond what the schema provides, so it neither helps nor detracts.

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 'Create a cron job.' clearly states the action and object, which is a specific verb+resource pair. However, it does not explicitly mention the 'agency' context, and with sibling tools like hosting_cron_create and agency_cron_delete, the description alone could be ambiguous without the tool name.

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 versus alternatives such as hosting_cron_create or agency_cron_list. The description provides no context for appropriate use, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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