bundle_import

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

With no annotations, the description must disclose behaviors. It mentions a conditional execution (plan by default, apply when write=true) but fails to explain what 'planning' entails, what side effects occur during apply, or any other behavioral traits.

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 sentence and concise, but the phrasing 'by default, or apply it only when write is true' is structurally ambiguous and could be misinterpreted.

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 complexity (4 parameters, no output schema, no annotations, multiple siblings), the description is extremely incomplete. It does not cover the overall purpose, parameter meanings, return values, or relationship to sibling tools.

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 0%, so the description must elaborate on parameters. It only mentions 'write' partially, leaving 'path', 'json', 'asNew' unexplained. This does not add meaningful semantics beyond the schema.

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 attempts to indicate a conditional behavior (plan vs apply based on write parameter) but is vague. It does not clearly state what 'structured task bundle import' means or how it differs from sibling tool 'bundle_import_plan'.

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. The description only implies behavior based on the 'write' parameter but does not provide context for choosing between bundle_import and bundle_import_plan.

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