production.animation_generation_render

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

Annotations mark it as mutating and non-idempotent; the description adds the dry-run default, immutable generation reference, retained Source Actions, and concrete errors for unsupported adapters. These are useful traits beyond structured fields, though the jargon limits clarity.

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?

It is compact, but front-loads an unhelpful 'M6 unit' label and packs opaque terms ('declared stage parameters', 'temporal artistic review') into short sentences. The brevity does not translate into clarity.

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?

With seven inputs, no schema descriptions, and a rich mutation flow, the description omits what the tool actually accomplishes and leaves most parameters unexplained. The output schema relieves return-value burden, but not the call-construction gaps.

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 coverage is 0% for seven parameters. The description only touches apply, generation, and options; brief, intent, object_name, and operation_id remain undefined, leaving key inputs opaque.

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 calls it a 'high-level M6 unit' but never states a concrete verb or resource. It alludes to planning and a generation reference, yet an agent cannot tell what animation_generation_render actually produces or how it differs from animation_generation_plan or animation_generation_compatibility.

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 sequencing ('Plan first') and a safe default ('apply=false by default'), plus prerequisites ('Explicit mapping and compatible body rig required'). It does not name when to choose this over animation_generation_plan or compatibility, nor when not to use it.

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