Delete a 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. It notes permanence ('Permanently delete') and scope ('by ID'), but does not mention required permissions, side effects (e.g., running jobs, dependent resources), or whether the deletion is irrevocable beyond the word 'permanently'.

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 short sentence that conveys the primary purpose and the key identifier. There is no redundant or filler content.

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 simple input schema (one required integer) and lack of output schema, the description suffices for basic invocation. However, for a destructive operation with no annotations, the absence of impact details (permissions, irrevocability side effects) leaves it slightly incomplete.

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 100%, and the parameter 'jobId' is already well described as the job's numeric ID. The description adds no new detail about how to find or format the ID, but the schema already sufficiently covers this.

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 clearly states the specific verb and resource: permanently delete a cron job by ID. It distinguishes the operation from siblings like get_job and list_jobs, although it doesn't explicitly contrast with delete_folder.

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?

The description conveys a clear delete action on a cron job, implying it should be used when the intent is to remove a cron job permanently. However, it does not specify when not to use it (e.g., soft delete or reversible actions), nor does it mention alternatives.

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