volume_create

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

Beyond annotations, the description reveals important behaviors: anonymous volumes accumulate unless containers use --rm or are removed with -v, and created volumes are stamped with provenance labels. This gives an agent crucial operational context beyond simple creation.

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 dense but every section contributes: usage context, lifecycle warnings, driver_opts examples, argument list, and return shape. The Args/Returns structure is easy to scan and front-loads the most important decisions.

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?

With no output schema, the description compensates by stating the returned dict and keys. It covers all four parameters, provides examples for the most complex one, and addresses lifecycle and cleanup concerns. Nothing critical for invoking the tool is missing.

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 schema description coverage at 0%, the description carries the param documentation burden. It adds real value for name (auto-generated anonymous volume) and driver_opts (with concrete local-driver examples), but driver and labels get only minimal elaboration beyond their names.

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?

Description opens with a specific verb and resource ('Create a volume managed by Docker') and immediately clarifies the key distinction between named and anonymous volumes. It also implicitly differentiates from volume_list, volume_prune, and volume_remove by naming them later.

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 explicitly tells when to use volumes ('for databases, uploads, or any data that must outlive a container') and explains the lifecycle of anonymous volumes. It names sibling tools for listing (volume_list) and reclaiming (volume_prune), giving clear routing guidance.

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