Curated Collection Pack

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

With no annotations, the description must carry the full burden. It discloses the output structure (.pack/ directory tree with JSON and checksum manifests), actions (pack/unpack), and offline nature. But it omits details on failure modes, whether vault assets are modified, permissions required, or what 'provenance' entails — leaving gaps.

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 a tight, front-loaded paragraph of three sentences. Every word serves a purpose — no filler, no redundancy. It efficiently conveys purpose, actions, output format, and offline capability.

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 11 parameters and no output schema, the description provides a solid high-level understanding: actions, output structure, offline nature. It could detail error scenarios or what 'provenance + integrity' means, but for the schema coverage level it's sufficiently complete.

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 coverage is high (91%), so the baseline is 3. The description adds value by explaining the overall process: 'action=pack gathers items into a <name>.pack/ directory tree... action=unpack restores the tree', which ties parameters together and clarifies behavior beyond individual schema entries.

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 bundles curated vault assets into a portable pack with provenance and integrity. Distinguishes between pack and unpack actions. Although sibling packing tools exist (e.g., morph_pack, variant_pack), the description's specific verb 'bundles a curated, hand-picked set' and mention of 'provenance + integrity' set it apart.

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 notes the tool is 'fully offline — no TD bridge required', implying a use case for offline packing. However, it does not explicitly state when to use this tool versus alternatives like morph_pack or variant_pack, nor does it provide exclusions or prerequisites.

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