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

Annotations declare readOnlyHint=false (a write) and idempotentHint=true; the description usefully clarifies that despite being a write it does NOT generate content, spend credits, or publish, and that the resulting draft is inactive. This materially reduces the risk of an agent misreading the mutation. It does not describe persistence/side effects beyond that.

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?

Three terse sentences, front-loaded with the core action and followed by the non-obvious negative behaviors. Efficient, though the trailing 'only UGC storyboard frames; the saved automation type must match this tool' slightly overlaps with the purpose statement.

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?

With an output schema and annotations present, the description need not cover return values or safety, and it does cover the key behavioral caveats. But for a tool with a large nested recipe at 0% parameter coverage, it is too thin to fully guide correct invocation of the complex payload.

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 0% and there is a deeply nested 'recipe' object plus idempotencyKey and brandId. The description adds no meaning about any parameter, so an agent gets no help understanding the recipe's required sub-fields, timezone, caps, or idempotency semantics beyond what the raw schema shows.

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 outcome ('Save an inactive review draft') and names the resource ('UGC storyboard frames'), which distinguishes it from sibling prepare_* tools for other automation types. It stops short of explaining what the saved draft is for or how it differs from prepare vs. activate vs. update flows.

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 implies usage by negating generation/credit-spend/publishing and stating the automation type must match, suggesting this is the pre-activation save step. However, it never explicitly says when to choose this over siblings like activate_ugc_storyboard_automation or update_ugc_storyboard_automation.

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