Dpanel Cron Prune Log

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

With no annotations, the description carries full burden. It does the important work of flagging the operation as destructive and requiring an explicit confirm=true gate, but it does not disclose the scope of destruction (all logs for the task? older than a threshold?), reversibility, or any permission requirements.

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?

A single compact sentence with the destructive warning and confirmation gate front-loaded via parenthetical. No filler, though the parenthetical format is slightly dense for the amount of information conveyed.

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?

The output schema exists, so return values need no explanation. However, with no annotations and 0% schema coverage on a 2-parameter mutation tool, the description leaves the meaning of the required id and the precise scope of the pruning undefined, which is a meaningful gap for a destructive operation.

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%, so the description must compensate for both parameters. It clarifies the confirm parameter's required value (true), but the required id parameter is left completely unexplained — the agent cannot tell whether it is a task ID, a log ID, or something else.

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 specific verb+resource ("清理计划任务日志" = prune/clean cron task logs), which distinguishes it from the read-only cron siblings like dpanel_cron_log_list and dpanel_cron_detail. It does not, however, explicitly name those siblings or clarify how pruning differs from deleting a task (dpanel_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?

The description states a prerequisite ("需 confirm=true") rather than when-to-use guidance. It implies this is the tool for removing cron logs but never contrasts it with dpanel_cron_log_list (view logs) or dpanel_cron_delete (remove the task itself), leaving the agent to infer the selection boundary.

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