cron_add

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'Create a cron job.' It does not mention persistence, validation requirements, whether client_id must reference an existing client, idempotency, or what happens on duplicate submissions.

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 immediately conveys the core action. It is efficient and front-loaded, though it could have incorporated additional behavioral or usage context without becoming verbose.

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 creation tool with a nested, loosely-specified params object, no output schema, and no annotations. The description does not explain required fields inside params, execution schedule semantics, response format, or side effects, leaving significant gaps for an agent that must construct a valid call.

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 documents both parameters with 100% coverage: client_id as 'Client ID' and params with a description listing example keys like server_id, parent_domain_id, command, run_min, and run_hour. The description itself adds no parameter information beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific action and resource: 'Create a cron job.' This clearly identifies the operation as the creation counterpart to sibling tools like cron_list, cron_update, and cron_delete, though it does not add detail about what constitutes a cron job beyond the 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 about when to use this tool versus alternatives — no mention of using cron_update for modifications or cron_list for viewing existing entries. The intended usage is only implied by the tool name and description, with no exclusions or context.

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