Create Mogrt Batch

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

The description discloses key behaviors beyond the annotations: it requires explicit export confirmation, stops on the first After Effects failure, and does not claim rollback. This is valuable safety-relevant context that is not present in the annotations or schema descriptions.

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 tightly written sentences deliver the essential purpose, prerequisite, and failure behavior with no filler. The most important information is front-loaded and every clause earns its place.

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 prerequisite (batch preview token), the required confirmation flag, and the failure/rollback behavior. With an output schema present, return-value details are already handled elsewhere, and nothing critical is missing for selecting and correctly invoking this tool.

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%, and both parameters are already clearly explained in the schema. The description adds no parameter-level detail beyond what the schema provides, so the baseline score applies.

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 the exact MOGRT recipes') and identifies the source ('from a one-time batch preview'), distinguishing it from single-recipe creation or preview-only tools. The schema's preview_token reference to preview_mogrt_batch reinforces this unique scope.

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 clearly implies when to use it: after a one-time batch preview and only with explicit export confirmation. It does not explicitly name alternatives or exclusions, but the batch-preview context and the token dependency provide strong usage guidance.

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