bundle_import

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

With no annotations, the description carries full behavioral transparency. It details the write import behavior: runs under a pack lock, creates a parked task with verification reset, retains the bundle and manifest, and never changes the current-task pointer. The default read-only plan behavior is also clearly stated.

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 four sentences, front-loaded with the core purpose, then default behavior, write behavior, and caution. Every sentence adds essential information without redundancy, making it concise and well-structured.

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 no output schema, the description explains the return value for the default mode (read-only plan) but does not explicitly describe the return format or error conditions for write mode. It covers the main behavioral aspects well but lacks some completeness regarding expected output and error handling.

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 100%, so baseline is 3. The description adds significant context to the 'write' parameter by explaining its effect on the import process. However, other parameters like 'asNew' and 'json' are not elaborated beyond the schema. The description adds value but does not fully compensate for all parameters.

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 'Import a task bundle into this pack' using a specific verb+resource structure. It further distinguishes itself from sibling tools like bundle_export, bundle_import_plan, and bundle_inspect by advising to 'Inspect or plan untrusted bundles first', indicating it is the actual import action while others are preview or 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 description explicitly explains the default read-only behavior vs. write behavior, and advises to use the tool for inspection or planning first. It provides clear context for when to use the tool (for preview or actual import) and suggests alternatives (inspect/plan) for untrusted bundles, offering strong usage guidance.

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