Dpanel Cron Delete

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation is destructive and requires confirm=true, which is essential for safe invocation. However, it omits other relevant traits such as permissions required, irreversibility beyond the word 'destructive', and whether logs or related data are also removed.

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, front-loaded sentence containing the operation, its destructive nature, and the confirm requirement. There is no wasted text. The structure puts the most important safety guidance immediately after the action.

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 an output schema, return values do not need explanation. The description covers the critical destructive warning and confirm gate, but with no annotations it should ideally say more about permissions, side effects, or what exactly is deleted. It is minimally adequate.

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 adds meaning for only one of the two parameters: confirm must be true despite the schema defaulting it to false. The required id parameter is not described beyond the operation name implying it identifies the scheduled task. This is partial compensation for the low schema coverage.

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 states a specific verb and resource: '删除计划任务' (delete scheduled task). It clearly distinguishes this from sibling tools like dpanel_cron_list, dpanel_cron_create, or dpanel_cron_prune_log. An agent can identify the operation without opening the schema.

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 implies the tool is used for deletion and adds a critical condition: '需 confirm=true'. However, it does not compare with alternatives such as dpanel_cron_prune_log or explain when deletion is appropriate versus other cron management actions. The guidance is implied but not explicitly framed around alternatives.

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