Create Mogrt Batch

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

Goes beyond annotations to disclose important failure semantics: it stops on the first After Effects failure and does not claim rollback, which warns the agent about partial completion. Annotations cover safety profile (readOnly=false, idempotent=false), so this is meaningful added context, though it omits specifics like rate limits or what artifacts remain after a failure.

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 tight sentences with no filler; the action is front-loaded and the constraints follow.

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?

Output schema exists so return values needn't be described, and the description supplies the confirmation requirement and failure behavior. It is essentially complete for a two-param tool, though it could note what happens to already-created recipes on failure.

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 parameters (preview_token, confirm_export) are already documented in the schema; the description only alludes to them ('one-time batch preview,' 'explicit export confirmation'). Baseline 3 is appropriate since the schema carries the load.

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?

States a specific verb ('Create') and resource ('MOGRT recipes') and ties it to 'a one-time batch preview,' which distinguishes it from the sibling preview_mogrt_batch without the agent needing to open either schema.

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?

Makes the precondition explicit ('Requires explicit export confirmation') and implies it follows preview_mogrt_batch, but never names the alternative or states when not to call it.

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