prune_containers

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

Annotations already indicate idempotentHint and destructiveHint. The description adds safety detail that running containers are never affected and specifies return structure. No contradiction.

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?

Concise, front-loaded with purpose, then safety, preview, filter details, alternative, param description, and return format. Every sentence adds value, no fluff.

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 the tool's simplicity (one optional param), the description covers all necessary aspects: what it does, safety, preview, filter details, return dict, and alternatives. No gaps.

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?

While schema only defines filters as object with no sub-schema, description compensates by listing valid filter keys (until with formats, label) and usage details. Schema coverage is 0% but description covers essential semantics.

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 all stopped containers to reclaim disk space', specifying the action, resource, and purpose. It distinguishes from sibling prune tools like prune_images, prune_volumes, and prune_networks by focusing on containers.

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?

Explicitly notes that only stopped containers are affected and running containers are safe. Provides preview suggestion with list_containers, details filter keys, and directs to prune_managed prompt for broader cleanup.

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