export_container

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

Adds details beyond annotations: in-band return, size cap, base64 encoding, default value, and error behavior (ValueError). No contradictions.

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?

Well-structured with separate sections for args/returns, front-loaded main purpose, every sentence adds value, no wasted words.

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 all necessary aspects: what it does, when to use alternative, parameter details, return type, error condition, and output schema exists for return structure.

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?

Since schema has 0% description coverage, the description fully explains both parameters: id_or_name (container id/name) and max_bytes (abort if exceeded, default 32 MiB), adding value.

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 tool exports a container's filesystem as a tar archive and distinguishes it from the sibling export_container_to_file by specifying in-band return.

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?

Explicit guidance: prefer export_container_to_file for large containers due to size caps (32 MiB) and base64 encoding, naming the alternative.

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