Remove container

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

Explicitly states 'This is destructive and cannot be undone', which is critical behavioral info. Also notes force requirement. No annotations, so description carries full burden; largely sufficient.

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?

Three concise sentences, key action first, no redundancy. Every sentence adds value.

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?

Covers usage, destructiveness, force requirement. Missing mention of removeVolumes parameter, but overall adequate for a removal tool with no output schema.

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 parameters fully. Description adds context for force (needed for running containers) but not for container or removeVolumes. Baseline 3 is appropriate.

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 'Remove a container' (specific verb+resource) and distinguishes from siblings by advising 'prefer stopping first', implying stop_container as an alternative.

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 clear context: 'Requires `force` to remove a running one' and recommends 'prefer stopping first'. Does not explicitly list when not to use, but offers implicit guidance.

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