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

The description begins with a `[read, AI]` tag, which directly contradicts the annotations `readOnlyHint: false` and `destructiveHint: true`. Because the annotation says this is a non-read-only, destructive operation while the description presents it as a read operation, the behavioral disclosure is actively misleading.

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 dense but well front-loaded: purpose and return shape come first, followed by parameter guidance and downstream workflow. It is a single run-on block rather than bulleted, but every sentence carries useful information and there is little wasted text.

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 a complex 9-parameter tool with no output schema, the description does a good job explaining the returned scene structure, parameter constraints, and downstream tool sequence. However, it fails to explain the destructive/non-read-only side effects declared in annotations and does not clarify its relationship to the sibling `create_storyboard`.

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 must carry the parameter burden; it does so well, covering `scenario` character limits, `count` range, `characters` limits, `language`, the `ai` provider enum, and the `scene`/`note`/`context`/`style` rewrite mode. Some details about the object shapes are implicit rather than fully spelled out, keeping it just below a 5.

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 that this tool generates a film storyboard via a chosen AI account and even describes the returned `data.scenes` structure. It does not distinguish itself from the sibling `create_storyboard`, which is a notable gap, but the core purpose is specific and actionable.

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?

It gives explicit workflow guidance: use `scenario` to plan the film, use the `scene` + `note` form to rewrite a single scene instead, then call `create_character_image` and `create_film_video`. It lacks an explicit comparison against the sibling `create_storyboard`, so the guidance is strong but not exhaustive.

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