delete_crons

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

With no annotations, the description carries the transparency burden. It does disclose the critical trait of irreversibility with a warning emoji, which is valuable. However, it does not mention permissions, side effects on associated data (e.g., logs), or partial deletion behavior, so it provides only minimal behavioral context beyond the action itself.

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 extremely concise, with two short sentences that immediately convey the action and a critical warning. Every word is meaningful, and it is appropriately front-loaded.

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 one parameter, the description covers the core action and a warning. However, it lacks details about return values, error handling (e.g., partial deletion), or any usage constraints, which would be helpful for an agent to invoke it correctly in all scenarios.

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 schema already fully describes the parameter (ids as an array of numbers with 'Array of IDs'). The description's phrase 'by ids' adds no additional semantic detail about the IDs' meaning, format, or constraints. Given 100% schema coverage, the baseline of 3 applies.

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 function with a specific verb ('Delete') and resource ('cron tasks'), plus the method ('by ids'). It unambiguously distinguishes from sibling tools like list_crons, create_cron, and update_cron, and is not a tautology.

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 guidance is provided on when to use this tool versus alternatives, any prerequisites, or exclusions. The description only states what it does, leaving the agent to infer usage entirely from the tool's name and the destructive context.

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