cron_delete

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly labels the operation as destructive ('Delete') and flags confirm as required, which is useful. However, it does not state whether deletion is permanent, what happens when confirm is false, or what authorization implications impersonate carries.

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 purpose is stated in one punchy sentence, followed by a tight Args block with no filler. Every line adds operational value, and the most important guardrail (confirm) is included without extra prose.

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 simple destructive operation with an output schema, the essential context is present: target identification, owning user, and confirmation. It could explicitly mention irreversibility or the consequence of omitting confirm, but an agent has enough information to make a correct 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?

Schema description coverage is 0%, and the description compensates by explaining all three parameters: job_id comes from cron_list's select0 value, impersonate is the owning user, and confirm is required. The only ambiguity is 'confirm: Required' against the schema's default false and non-required status, but the intent is reasonably clear.

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?

States a decisive verb and resource: 'Delete a cron job'. It also identifies the exact identifier source ('panel id / select key') and the argument docs reference cron_list, which distinguishes it from the cron_create and cron_list siblings.

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 gives clear operational context by saying the job_id comes from cron_list and that confirm is required. It does not explicitly compare against sibling tools, but it communicates the prerequisite and safety condition needed to invoke the tool correctly.

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