delete_cronjob

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It does not state that the deletion is destructive/irreversible, whether confirmation or elevated permissions are required, or what happens to a running cronjob.

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?

It is a two-word phrase with no waste, but this is under-specification rather than effective conciseness. There is nothing front-loaded because there is essentially nothing to front-load.

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?

For a destructive mutation with no annotations, no output schema, and an undocumented required parameter, the description is completely inadequate. An agent cannot determine irreversibility, target semantics, or expected outcome from this definition.

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 0%, so the schema documents nothing about the single required `id` parameter. The description does not mention it at all, leaving ambiguous whether it is a numeric job ID, name, or index, so no meaning is added beyond the raw type.

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?

"Delete cronjob" states a specific verb (delete) and resource (cronjob), so the basic operation is identifiable. However, it adds nothing beyond the tool name itself and does not distinguish this from siblings like list_cronjobs or create_cronjob, nor clarify scope (single job by ID vs bulk).

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 versus the sibling cronjob tools, no prerequisites (e.g., does the job need to be stopped first?), and no exclusions. The agent is left to infer everything from the name.

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