plur_packs_export

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

Annotations provide non-idempotent and non-destructive hints. Description adds behavioral details: automatic filtering of private engrams, integrity hash generation, default output directory. 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?

Two sentences, front-loaded with key action and features. No extraneous information. Every sentence adds value.

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 8 parameters and no output schema, the description covers purpose, default behavior, and filtering. It lacks details on output format or return values, but the tool's name and context make the intent reasonably clear.

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 description coverage is 100%, so each parameter has a description. The tool description adds minimal extra meaning beyond the schema (e.g., default output dir). Baseline is 3 for high 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?

The description clearly states the tool exports engrams as a shareable thematic pack with privacy scanning and integrity hash. It distinguishes from sibling tools like plur_packs_install and plur_packs_list by focusing on export functionality.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., plur_packs_preview). It implies it's for exporting packs but doesn't specify contexts such as 'use when you need a shareable package' or 'avoid when you just want to preview'. No exclusions or when-not-to-use advice.

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