production.animation_spline

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

Annotations already disclose the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), lowering the disclosure burden. The description adds useful context that generation is an immutable plan.json reference, Source Actions are retained, and unsupported adapters return concrete errors, but it still does not explain exactly what apply mutates or what side effects occur.

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 not overly long, but it is dense with jargon like "high-level M6 unit" and semicolon-separated caveats. The plan-first constraint is front-loaded, yet the opening phrase is cryptic rather than orienting.

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?

This is a complex mutation-capable animation tool with seven parameters, an output schema, and many close siblings. The description provides some operational caveats, but it is not complete enough to tell an agent what the tool actually does, which parameters are central, or how it relates to alternatives.

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% for seven parameters, so the description must carry parameter meaning. It only clarifies apply/default, generation as a plan reference, and options as stage parameters/thresholds/review, while brief, intent, object_name, and operation_id remain undocumented.

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 this a "high-level M6 unit" but never states a clear verb-and-resource purpose such as generating, planning, or applying a spline animation. It mentions plan-first behavior and prerequisites, but an agent cannot confidently distinguish it from siblings like animation_generate, animation_generation_plan, or animation_refine_generated.

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 some useful invocation guidance: plan first, apply defaults to false, explicit mapping and a compatible body rig are required. However, it does not say when to use this tool versus the many adjacent animation generation/planning siblings, nor does it state 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.