Delete container

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

Annotations already indicate destructive action. Description adds 'permanently' and explains behavior of force and volumes, exceeding annotations. Still lacks detail on return values or side effects.

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?

Single sentence with risk warning and parameter usage. No wasted words, front-loaded with key information.

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?

Given no output schema and rich sibling context, description adequately covers tool behavior. Optional parameters explained. Could mention that deletion is irreversible, but 'permanently' implies it.

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 covers 100% of parameters. Description adds meaning beyond schema descriptions: force deletes running containers, volumes removes associated volumes. This improves usability.

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?

Clearly states 'Delete a Docker container permanently' with a specific verb and resource. The [HIGH RISK] tag and mention of force/volumes distinguish from sibling tools like stop, restart, or redeploy.

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?

Provides guidance on when to use force and volumes parameters but does not explicitly contrast with alternatives (e.g., stop vs delete) or state when not to use.

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