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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: credit caps are consumed, previously approved automatic delivery can publish to connected channels (an outward-facing side effect), and only original generated images are in scope.

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 tight sentences with the action front-loaded and no filler. Each sentence carries a distinct constraint, though the flow between the publishing side effect and the image-scope note is slightly abrupt.

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 the description covers credits, delivery side effects, and type-matching. However, for a destructive, idempotent mutation with a revision guard, the description never explains how revision or idempotencyKey should be supplied, leaving a notable gap.

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% across four required parameters, so the description carries the full explanatory burden. It only loosely alludes to 'the saved recipe' and 'automation type' without clarifying brandId, revision (a concurrency/version token), or idempotencyKey, leaving the most failure-prone parameters undocumented.

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 ('resume') and resource ('recurring generation'), and adds the scope constraint that the saved automation type must match this tool, which helps distinguish it from the many resume_* siblings. It stops short of naming a specific alternative sibling, so it is clear but not maximally differentiated.

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?

Implies usage via 'resume recurring generation' and the constraint that the saved automation type must match, but never states when to prefer this over activate_* or prepare_*, nor any preconditions such as the automation needing to be paused first. Usage is inferred rather than specified.

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