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

Annotations cover the mutation/safety profile, and the description adds real behavioral value beyond them: the style-template prerequisite, the dedupe of assets already rendering, and the billing guarantee that a repeat never bills twice. It does not describe failure handling or timing, so not a 5.

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?

Four sentences, front-loaded with the purpose before prerequisites and follow-up. Minor redundancy between 'skipping ones already rendering' and 'a repeat never bills twice', but nothing wasted overall.

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 non-destructive mutation with full annotation coverage and no output schema, the description supplies the prerequisite, default-omission behavior, billing/dedupe semantics, and a verification step. It omits only secondary details like timing and error behavior.

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 the baseline is 3. The description restates asset_ids omission behavior (render every asset with none) and adds the style-template requirement, but adds little on model, settings, editable_sections, or dry_run beyond what the schema already says.

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?

States a specific verb (render) and resource (reference images) and explains their role: keeping characters/environments/objects consistent across segments. It names the sibling view_image as a follow-up step, though it does not explicitly contrast itself with style_generate or storyboard_generate.

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 a precondition (both style template images needed) and a follow-up workflow (view_image to check likeness), plus the effect of omitting asset_ids. It stops short of naming an explicit alternative tool to use instead for a different case.

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