motion vfx create

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

Fails to disclose side effects, such as whether the recipe is persisted, overwritten, or if repeated calls create duplicates. Annotations indicate idempotentHint false but the description does not surface this or any other behavioral details.

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 concise, with two sentences. It front-loads the primary purpose. However, the second sentence about reading and revising could be confusingly coupled to the creation action, slightly affecting 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?

The description lacks information about the output or return value, even though an output schema exists. It also does not clarify how the created recipe integrates with sibling tools (e.g., saving to library or studio), leaving gaps in the operational context.

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?

Parameter names 'name' and 'preset' are self-explanatory, but the enum values ('charge', 'impact', 'heal') are not explained. The description mentions editable properties like color and size, but these do not map to the actual parameters, and schema coverage is 0%.

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?

Clearly states it creates an editable native Roblox particle recipe, which is a specific action. The verb 'create' is unambiguous, and the resource is a particle recipe. It differentiates from sibling tools that handle animations or library operations.

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?

Does not specify when to use this tool versus alternatives like motion_library_save or motion_studio_save_vfx. It mentions reading and revising the recipe but does not clarify under what conditions this tool is preferred or if it complements other workflow steps.

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