Create Mogrt Recipe

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

With annotations already declaring the write/non-idempotent/non-destructive/non-open-world profile, the description adds useful constraints beyond them: it won't create projects or output folders and it lands in a saved project inside an approved workspace. It does not restate idempotency or describe failure/side effects on the AE project, so not a 5.

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 the core operation front-loaded and the confirmation constraint plus scope limitations following. No redundancy or filler.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description supplies preconditions and scope limits, making it adequate for a mutating tool; only the linkage to the preview/token-producing sibling is left implicit.

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 fully documented in the schema. The description only echoes the confirmation requirement, adding no syntax or format detail beyond what the schema already provides; baseline 3 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?

States a specific verb and resource ('Create exactly one previewed MOGRT recipe') plus the target environment (saved AE project in the approved workspace). The word 'exactly one' cleanly differentiates it from the sibling create_mogrt_batch, and 'recipe' from preview_mogrt_recipe.

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?

Gives a clear precondition ('Requires explicit export confirmation') and an explicit negative ('it never creates projects or output folders'). It implies but does not name the prerequisite sibling preview_mogrt_recipe that issues the token, so it falls short of full when/when-not/alternatives guidance.

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