Dpanel Image Build Delete

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

With no annotations, the description carries the full burden; it usefully discloses that the operation is destructive and needs confirm=true, which is behavior beyond the bare schema. However it says nothing about permissions, whether the deletion is reversible, or side effects on running builds.

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 short sentence with the critical destructive/confirm warning front-loaded after the verb. Efficient, though the brevity leaves gaps given zero schema coverage.

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?

An output schema exists so return values need not be described, which helps. But for a destructive tool with no annotations and 0% schema coverage, the description is thinner than ideal, notably omitting any meaning for the id parameter.

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 schema provides no parameter meaning. The description adds value by tying confirm=true to the destructive nature, but the required id parameter is left entirely unexplained.

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 (镜像构建任务), clearly distinguishing it from dpanel_image_delete and dpanel_image_build_prune. It is unambiguous what the tool acts on, though it does not explicitly name its siblings.

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 notes the operation is destructive and requires confirm=true, but gives no guidance on when to use this over alternatives such as dpanel_image_build_prune, nor any prerequisites. Usage context is only loosely implied.

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