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

Annotations already declare destructiveHint=true and idempotentHint=true, so the mutation and retry model is covered. The description adds genuine context beyond that: activation is bounded by 'credit caps', and 'previously approved automatic delivery can publish to connected channels' discloses an external side effect (channel publishing) the annotations only hint at via openWorldHint.

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 with the core action front-loaded and no filler. The third sentence is terse to the point of ambiguity ('Only original generated images'), but it earns its place as a scope limit.

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 annotations cover safety. The description adequately covers scope, credit limits, and channel side effects, but with 0% schema coverage on four required parameters and no mention of the prepare/approve prerequisite workflow, an agent still lacks the full picture for correct invocation.

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 coverage is 0%, so the description must carry the parameter burden for 4 required fields. It vaguely references 'the saved recipe' and 'saved automation type', which loosely point at automationId, but brandId, revision, and especially idempotencyKey (critical for a mutation with idempotentHint) are entirely unexplained.

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) and resource (recurring generation from a saved recipe), which distinguishes it from resume_*, prepare_*, and update_* siblings. The clause 'the saved automation type must match this tool' routes it within the large activate_* family, though it never names the image-generator recipe explicitly as the required match.

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 constraint 'the saved automation type must match this tool' is an implied precondition for use, and 'using the saved recipe' implies a prior prepare/approve step. However, the description never states when to use activate versus resume_* or update_image_generator_automation, leaving the agent to infer the activation lifecycle.

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