Delete Cron Job

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

The annotation destructiveHint=true already signals the destructive nature, and the description 'Delete a cron job' is consistent with that. However, the description adds no additional behavioral context (e.g., irreversibility, consequences) beyond what the annotation provides.

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, concise sentence with no filler. It is front-loaded and every word earns its place, though it is minimal.

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 delete tool with two fully described parameters and a destructiveHint annotation, the description is adequate but sparse. It does not mention potential pitfalls, prerequisites, or what happens after deletion, which would improve completeness.

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% (both 'uid' and 'username' have descriptions), so the schema carries the parameter meaning. The description adds no further context about how the parameters relate to the deletion process.

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 'Delete a cron job' clearly states the action (delete) and the resource (cron job). It is unambiguous and consistent with the tool name and title. It distinguishes from create/list cron tools by specifying deletion, though it doesn't explicitly differentiate from agency_cron_delete.

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 on when to use this tool, prerequisites, or alternatives. The one-sentence description gives no context about needing existing cron job UIDs or how this fits into cron management workflows.

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