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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description does not need to restate the mutating nature. The description adds useful operational context beyond annotations: the batch plan limit precondition, the zero-limit fallback to individual calls, and the per-image output shape (IDs, URLs, format in item). No contradiction with annotations.

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?

Three sentences cover purpose, precondition, alternative tooling, and return information without filler. The core function is front-loaded, and each sentence earns its place.

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 rich schema, output schema, and annotations, the description covers the essential operational guidance: call get_max_batch_size first, respect the limit, fall back to individual calls when needed, and expect per-image IDs/URLs/format. It could name the specific individual creation tools, but the generic reference combined with the sibling list is sufficient for an agent to route 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?

Schema description coverage is 100%, so each parameter and nested property is already thoroughly documented. The description adds the high-level relationship that variations override default_options, but this largely summarizes what the schema already states. Baseline 3 is appropriate because no genuinely new parameter semantics are introduced.

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 states a clear verb-resource pair ('Creates multiple image assets') and explains the batch structure of shared defaults plus per-item variations. It also contrasts with 'individual creation tools' in the final sentence, letting an agent distinguish it from create_image, create_url_image, and create_templated_image.

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?

Explicitly instructs callers to invoke get_max_batch_size first and stay within the returned plan limit, including the edge case where a limit of 0 forces individual image calls. It also states when to use individual creation tools instead: when only one image or an inline preview is needed.

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