motion studio save vfx

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

The description discloses undoability, the creation of an Attachment, a disabled ParticleEmitter, and that EmitCount records the burst amount. This complements the readOnlyHint and destructiveHint annotations, with no contradiction.

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?

Two concise sentences front-loaded with the primary action and key details. No filler or redundant phrasing.

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?

The description covers the core mutation and undoability, but omits semantic details for assetId and part. The output schema and annotations help, yet the parameter gaps leave moderate ambiguity.

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?

Only rigId and sessionId have schema descriptions. 'part' and especially 'assetId' lack meaningful descriptions, and assetId is defined via a confusing reference to sessionId. The description does not clarify what assetId or part represent.

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?

Description clearly states a specific action: saving a library VFX recipe as a new Attachment and disabled ParticleEmitter on a uniquely named part. It is easily distinguished from sibling tools like motion_studio_save_animation and motion_vfx_create.

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?

No guidance on when to choose this tool over alternatives such as motion_vfx_create or motion_library_save. The description implies a scenario but never explicitly states use cases or exclusions.

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