bundle_export

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

With no annotations provided, the description carries full burden. It discloses that it writes a new file at outputPath and that pack state is unchanged. Parameter description also reveals constraints (new repo-relative path outside .agentpack/ and .git/, rejects existing files). Does not mention permissions or reversibility, but covers key side effects.

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 with no waste. First sentence states purpose and content; second sentence adds behavioral trait and location. Front-loaded and efficient.

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 tool with 4 parameters (100% schema coverage) and no output schema, the description adequately covers purpose, key behavioral trait, and parameter context. It lacks details on return values or error conditions, but the tool's simplicity and schema coverage mitigate this.

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% (baseline 3). Description adds value by clarifying defaults (taskId defaults to current task), explaining sources as 'repo-relative source paths whose Source Cache records to include', and detailing outputPath constraints. This goes beyond the schema's brief 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?

Description clearly states the verb 'export', the resource 'Task Passport with its decisions, dead ends, source conclusions', output format 'redacted agentpack.task-bundle JSON', and purpose 'sharing tasks across repos, machines, or agents'. It distinguishes from siblings like bundle_import by focusing on export.

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 purpose implies usage context (sharing across repos, machines, agents), but the description does not explicitly state when to use or not use this tool versus alternatives. No exclusions or when-not-to-use guidance.

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