Create recurring 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. It only says 'Create' and provides a docs link; it does not mention idempotency, duplicate-name behavior, validation requirements, permissions, or side effects of creating a recurring 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 short and front-loaded, with no filler, and the docs link is a useful pointer. However, for an 8-parameter creation tool, the terseness borders on under-specification rather than disciplined conciseness.

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 no annotations, no output schema, nested objects, and 5 required parameters, the description is not complete enough for reliable invocation. The external docs link helps, but the MCP description itself leaves essential behavioral and parameter context unexplained.

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 description coverage is only 25%, covering cron and task, while required fields like name, retain, and concurrency plus optional groups, labels, and parameters are left unexplained. The description adds no parameter-level meaning and does not compensate for the low 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 clear verb-resource pair ('Create a new Longhorn recurring job') and names the domain-specific resource, which distinguishes it from list/get/update/delete siblings. It does not articulate scope or nuances beyond creation, but the core purpose is 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?

No guidance is provided about when to call this tool versus alternatives such as recurringjob_update or volume_recurring_job_add. The description does not mention prerequisites, typical workflow steps, or exclusions, leaving the agent to infer usage from the sibling names alone.

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