Dpanel Container Backup Delete

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

With no annotations, the description carries the safety burden. It discloses that the operation is destructive ('破坏性') and requires confirm=true, which are important behavioral traits beyond the schema. It does not mention irreversibility, permissions, or what happens to the backup data afterward.

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?

One short sentence front-loads the action, flags destructiveness, and states the required confirmation. Every word earns its place with no redundancy.

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 description covers the core destructive nature and confirmation requirement, and an output schema exists so return values need no explanation. It is nearly complete for a simple delete operation, though it could clarify the id parameter and irreversibility.

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 coverage is 0%, so the description must compensate. It adds crucial meaning for the confirm parameter (must be true to proceed), but the id parameter remains undocumented beyond its type. Partial compensation justifies a middle score.

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 and resource: '删除备份' (delete backup). This clearly distinguishes it from sibling backup tools like backup_create, backup_restore, backup_list, and backup_detail. No explicit sibling naming, but the action is unambiguous.

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 use for deleting a backup and adds the critical requirement '需 confirm=true' (requires confirm=true). However, it does not state when to choose this over alternatives or any exclusions, leaving context to inference.

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