Pack / unpack a create_preset_morph slot set to a vault JSON

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the agent knows this tool mutates state. The description adds useful behavioral context: packs are sha256-verified, the tool reuses the existing engine rather than creating new topology, and unpack can rebuild missing containers. It does not mention merge=replace wiping presets in the description, but the schema covers that and there is no direct contradiction.

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 three sentences, each earning its place: first defines both modes, second clarifies engine reuse and topology compatibility, third gives the environment prerequisite. It is front-loaded and compact without unnecessary filler.

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?

For a dual-mode tool with 9 parameters, the description plus rich schema is sufficient for correct invocation. It includes the key prerequisite (TDMCP_VAULT_PATH) and the container-creation behavior. Return values/provenance details are not described, but the absence is not critical given the schema and sibling context.

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 covers 100% of parameters with detailed descriptions, so the baseline is 3. The description adds a high-level mental model (pack vs unpack, inline looks exception) but does not add meaning beyond what the schema already provides for each parameter.

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 a specific action: export a create_preset_morph container's slots to a sha256-verified vault JSON (pack) or re-hydrate a pack back into a container (unpack). It names the exact resource and distinguishes the two modes, which also differentiates it from sibling tools like create_preset_morph or manage_presets.

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 gives clear usage context: it explains both actions, states that the tool reuses the existing create_preset_morph engine, and notes the TDMCP_VAULT_PATH requirement unless inline looks are supplied. It does not explicitly name alternative tools or state when not to use it, but the context is strong enough to guide correct selection.

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