bundle_import_plan

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

With no annotations, the description carries the full burden. It discloses a critical behavioral trait: the tool does not write pack state, indicating a non-destructive operation. However, it lacks details on other behaviors like validation, return format, or side effects, which are important for a planning tool.

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 a single, focused sentence with no extraneous information. However, it could be more structured with separated sections for purpose, usage, and parameters without sacrificing brevity.

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 has three parameters, no output schema, and no annotations, the description provides only the core purpose and one behavioral constraint. Missing are parameter details, output expectations, and guidance on how the plan is returned or used. The description is insufficient for an agent to use the tool correctly.

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 has three parameters (json, path, asNew) with 0% schema description coverage. The description does not explain any parameter's purpose, data type, or expected values, leaving the agent to guess. This is a significant omission.

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's purpose: planning a structured task bundle import without writing pack state. It uses a specific verb ('plan') and resource ('structured task bundle import'), and includes a key constraint that distinguishes it from related tools like bundle_import.

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 such as bundle_import or bundle_export. The description implies planning before actual import but does not provide context on prerequisites, when not to use, or comparisons with siblings.

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