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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is partly covered. The description adds meaningful context beyond them: previously approved automatic delivery can publish to connected channels, and credit caps apply — disclosing the concrete downstream consequence and cost dimension of activation.

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 compact sentences that are front-loaded with the activation purpose, followed by consequence and constraint. No filler, though the third sentence packs two distinct constraints that could be separated for clarity.

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 described. For a destructive mutation tool this is adequate on behavior, but the near-total absence of parameter guidance at 0% schema coverage leaves the agent under-informed about revision and idempotencyKey semantics.

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 (brandId, automationId, revision, idempotencyKey), so the description carries the full burden and largely fails. 'Saved recipe' loosely gestures at the automation reference, but revision, idempotencyKey, and brandId receive no explanation anywhere.

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 ('Activate recurring generation using the saved recipe'), and adds scope constraints ('Only retouched source images') plus a discriminator against the large activate_* sibling cluster ('the saved automation type must match this tool'). It does not explicitly name a sibling like prepare_retouch_automation, so differentiation is present but not sharp.

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?

Provides a precondition ('saved automation type must match this tool') and a scoping rule (only retouched source images), which implies when it applies. However, it gives no guidance on when to choose this over prepare_retouch_automation, resume_retouch_automation, or update_retouch_automation, leaving the agent to infer the alternative.

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