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

With `destructiveHint: true` already declared, the description adds substantive behavior: `all` redraws the whole stage vs. only missing entries, several stages always redraw every character list entry, reference resolution falls back through `reference_asset_id` → `character_reference_asset_id` → main picture, and the call answers `queued`/`skipped`. The one gap is that it never says whether redrawing replaces or duplicates existing assets, which is exactly what the destructive hint warns about.

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 write/queued/priced tag and the stage verb are front-loaded, and every clause carries a fact — no filler. It is, however, a dense run-on with nested parentheticals that an agent must parse carefully, which costs it a point on readability rather than on waste.

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?

For an async, queueing mutation with no output schema, the description supplies prerequisites, the conditional redraw rules, the response shape (`queued`/`skipped`), and the polling tool. Nothing an agent needs to invoke it correctly is missing.

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%, so the description carries the full load and does: it enumerates the `stage` values with per-value meaning despite no schema enum, defines `all` as redraw-everything vs. missing-only, defines `extra_prompt` as appended to each prompt, and defines `reference_asset_id` including its fallback source. Only `character_uuid` is left implicit, and its meaning is self-evident.

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?

Opens with an explicit verb+resource ("Queue the pictures of one stage of a character") plus the owning worker (`worker_characters_generate`), and immediately enumerates the full set of stage values. An agent can distinguish this from `create_character_image`, `create_character_thumbnail` or `edit_character` without opening any schema.

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?

Gives real preconditions (needs an AI account; needs a main picture except for MAIN and LOCATIONS; PROFILE requires a BIOMETRIC picture instead) and states how to follow up ("Poll with get_character"). It does not say when to prefer this over sibling `create_character_image`, so the boundary with single-image generation is left implicit.

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