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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true. The description adds non-obvious behavior: it does not publish, it draws on credit caps (a cost/billing consequence), and it requires the saved automation type to match. This is real context beyond the annotations, though it omits the approval lifecycle implied by the sibling approve_automation_sample.

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 short, front-loaded sentences with no filler, leading with the core action and following with the key constraints. Efficient, though the second and third sentences could be tightened into a single constraint clause.

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 not be explained. But with four required parameters at 0% schema coverage and no parameter guidance, plus an unmentioned approval step, the definition leaves meaningful gaps for an agent to fill before invoking it correctly.

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 all four parameters (brandId, automationId, revision, idempotencyKey) are undocumented in the schema. The description only loosely implies automationId must reference a saved automation of the matching type; it says nothing about revision or idempotencyKey semantics, so the description fails to compensate for the coverage gap.

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 gives a specific verb (generate) and resource (paid review sample from the saved recipe), and adds scope ('Only written reel concepts'). It partially differentiates from the many sibling generate_*_automation_sample tools via 'the saved automation type must match this tool', though the phrase 'paid review sample' is somewhat internal jargon an agent must infer.

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?

It provides a negative usage signal ('Does not publish') and a precondition ('the saved automation type must match this tool'), which is more than nothing. However, it never names the relevant alternative steps in the workflow (e.g. prepare_reel_concepts_automation or approve_automation_sample), so the agent must infer when this step belongs in the sequence.

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