Curated Collection Pack

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

The description reveals key behaviors: it creates a directory tree, writes a JSON manifest and checksum manifest, and supports integrity verification on unpack. These details go beyond the annotations (readOnlyHint=false, destructiveHint=false) which only indicate it is not read-only and not destructive. No contradictions with annotations are present.

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 concise (4 sentences) with the main purpose front-loaded. Every sentence adds meaningful information: bundling assets, actions, manifest details, offline nature. No redundant or vague statements.

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 complexity (11 parameters, two actions, nested items array) and the absence of an output schema, the description reasonably explains the overall workflow and outputs (directory tree, manifests). It covers the key behavioral aspects and constraints. A slight gap is the lack of mention of error conditions or the return value format, but the schema descriptions compensate.

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?

The input schema already provides detailed descriptions for 10 of 11 parameters (91% coverage). The description adds contextual value by explaining how the 'action' parameter drives different behaviors and how the 'name' parameter forms the output directory. This goes beyond the schema's individual parameter descriptions.

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 that the tool bundles vault assets into a portable pack with provenance and integrity. It specifies two distinct actions (pack/unpack) and the resulting outputs (directory tree, manifest). This distinguishes it from siblings like 'checksum_and_verify_pack' which focus on verification, or 'morph_pack' and 'variant_pack' which imply different transformations.

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 implies usage for creating portable, verified packs of assets, and notes that it works fully offline. However, it does not explicitly state when to use this tool versus alternatives such as 'morph_pack' or 'variant_pack', nor does it provide when-not-to-use guidance or prerequisites.

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