delete_container

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

Without annotations, the description explains key behavioral aspects: force flag to override running state, purge effect on replication/HA/backup/ACLs, and destroy_unreferenced_disks. It does not mention irreversibility but clearly indicates destructiveness.

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 concise: a single sentence for purpose followed by a bulleted parameter list. All information is relevant and front-loaded.

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 adequately covers purpose, preconditions, and parameter behavior, but does not mention the output schema or any post-deletion effects (e.g., irreversibility). Given the presence of an output schema, this is a minor gap.

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?

With 0% schema coverage, the description adds meaningful explanations for most parameters (e.g., purge removes from replication/HA/backup/ACLs) beyond the schema's titles and types. Node and vmid are self-explanatory from context.

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 clearly states the action 'Delete a container' and distinguishes it from sibling tools like delete_vm, clone_container, etc.

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 mentions the precondition 'Must be stopped first unless force=True' but does not explicitly compare with alternatives or provide when-not-to-use guidance.

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