container_archive_get

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

Discloses the 32 MiB default cap, in-band encoding overhead, and return format (archive bytes + stat dict), complementing the annotations (readOnlyHint=true, destructiveHint=false).

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?

Two short paragraphs with bullet-pointed args; front-loaded with purpose and alternative; no extraneous text.

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 aspects: purpose, when to use, parameter details, size limits, return structure. No output schema exists, but description sufficiently explains the result.

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?

Each parameter is explained: id_or_name as container identifier, path as container path, max_bytes with default and error behavior. Lacks detail on path format but compensates for 0% schema coverage.

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 it retrieves a file/directory as a tar archive and distinguishes from sibling `container_archive_get_to_file` by noting the in-band return and size cap.

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 instructs to use `container_archive_get_to_file` for large paths, and explains the `max_bytes` default and abort behavior.

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