create_cronjob

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

With no annotations, the description must disclose behavioral traits, but it says nothing about permissions, side effects, scheduling behavior, or what 'job' entails. It provides no behavioral context beyond the verb 'Create'.

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 only two words, which is concise but severely under-specified rather than appropriately sized. It fails to convey any necessary information for invocation.

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 a mutation tool with a nested object parameter, no annotations, and no output schema, the description is completely inadequate. It omits every detail an agent needs to call the tool correctly.

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 sole parameter 'job' is a nested object with 0% schema description coverage, and the description does not mention it at all. The agent has no information about required fields, format, or syntax for the job object.

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 cronjob' merely restates the tool name without specifying scope, constraints, or how it differs from sibling tools like list_cronjobs or delete_cronjob. It identifies the verb and resource but adds no differentiating detail, matching the rubric's tautology level.

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 when-to-use guidance, prerequisites, or alternatives are provided. The agent cannot tell when to prefer this tool over other creation tools or what conditions are required.

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