Dpanel Image Prune

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

With no annotations, the description carries the full burden and does flag the two things an agent most needs: this is destructive and it requires confirm=true (which the schema does not state, only a default of false). It doesn't define what counts as 'dangling' or whether the operation is irreversible.

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 sentence that front-loads the action, then the destructiveness warning and the required flag. Nothing extraneous.

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, and the destructive/confirm behavior is covered. Only the precise scope of 'dangling' images and any side effects remain unspecified.

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 single parameter 'confirm' has 0% schema description coverage, so the description must compensate — and it does, stating '需 confirm=true' as the required value. It adds the actual semantic (a safety gate) that the bare boolean schema lacks.

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 + scope: pruning '悬空镜像' (dangling images). The 'dangling' qualifier distinguishes it from dpanel_image_delete, though no sibling is named explicitly.

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?

Conveys the operational context (destructive cleanup of dangling images) and the confirm gate, but gives no explicit guidance on when to prefer this over dpanel_image_delete or dpanel_image_build_prune.

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