Create Mogrt Recipe

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

Annotations already signal that this is a non-read, non-idempotent, non-destructive action. The description adds useful behavioral boundaries: it never creates projects or output folders and requires explicit export confirmation. It could explicitly mention that the open AE project is saved, but the confirm_export parameter description covers that detail.

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 dense sentences front-load the core action and then add the most important behavioral caveats. There is no filler, and every phrase contributes either scope, a precondition, or a safety boundary.

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-trivial mutation/export tool, the description covers the key preconditions, constraints, and negative side effects. Combined with full schema descriptions and an output schema, it is sufficient for an agent to understand the workflow without needing return-value details repeated in prose.

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 both preview_token and confirm_export are already fully documented in the schema. The description adds only the general requirement of explicit export confirmation, which aligns with confirm_export but does not provide additional parameter-level meaning.

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 states a specific action—create exactly one previewed MOGRT recipe in a saved After Effects project—and clearly distinguishes it from preview-only and batch operations. Naming the scope ('saved project', 'approved workspace') helps an agent separate it from preview_mogrt_recipe and create_mogrt_batch.

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?

The description gives clear preconditions: the recipe must already be previewed, the project must be saved and in the approved workspace, and explicit export confirmation is required. It does not explicitly name alternatives or say 'do not use for batch', but the requirement of a preview token and 'exactly one' strongly imply the intended workflow.

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