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 genuinely new context beyond that: activation consumes 'credit caps' and 'previously approved automatic delivery can publish to connected channels', a real side effect an agent must weigh before calling. It does not explain revision-conflict or idempotency-key replay behavior, which keeps it short of 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?

Three short sentences, no filler, with the core action front-loaded and the precondition last. Every sentence carries information; nothing is repeated from the title.

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 annotations cover mutability and idempotency. The description supplies the two things an agent most needs for a destructive activation call — the credit cost and the possibility of publishing to connected channels — but leaves the four parameters, especially revision and idempotencyKey, unexplained.

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%, so the description carries the full burden for four required parameters, and it effectively documents none of them by name. 'Saved recipe' loosely gestures at automationId and 'must match this tool' hints at a type constraint, but brandId, revision, and idempotencyKey are never mentioned, leaving their meaning to be guessed from the schema patterns.

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 ('Activate recurring generation') and resource ('saved recipe'), and the closing clause 'the saved automation type must match this tool' differentiates it from the twenty-plus sibling activate_* tools. The recolor-specific scope ('Only recolored source images') is stated explicitly, though it is only marginally more informative than the name itself.

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 when to use it — activating an already-prepared recolor automation — and states a precondition ('the saved automation type must match this tool'). However, it never names alternatives such as resume_recolor_automation, pause_automation, or prepare_recolor_automation, so the agent must infer the lifecycle position rather than being told it.

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