Plan a portable Library or Published-template bundle

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

Annotations already declare readOnlyHint, destructiveHint=false, and idempotentHint. The description adds meaningful context about excluding rebuildable indexes/runtime locks and requiring an 'exact reachable Published Release', which enhances understanding beyond the annotations without contradicting them.

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 convey the core function and a critical behavior (writes nothing) with no wasted words. Information is 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?

The purpose and safety profile are clear, but the description omits any parameter semantics and the nature of the produced plan (e.g., format, content). Given the tool complexity (5 parameters, 2 required) and no output schema, this is incomplete for correct invocation.

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 0%, and the description does not explain any of the 5 parameters (kind, releaseId, targetName, templateId, destination). It gives a high-level overview but fails to compensate for the lack of schema details, leaving the agent without guidance on how to fill required fields.

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 inventories a library or published release and produces a directory-bundle plan, explicitly noting it writes nothing. This distinguishes it from apply_bundle_export and other plan/apply sibling pairs.

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 implies this is the planning step for bundle export, but it does not explicitly mention when to use it versus other planning tools or when not to use alternatives. The context of sibling plan/apply pairs makes the usage clear, but no explicit exclusions or alternatives are given.

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