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

Annotations already flag destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered; the description then adds genuinely new behavior — that previously approved automatic delivery will publish to connected channels, and that credit caps govern spend. It omits reversibility details (e.g., how to stop publishing, whether re-activation double-charges), which keeps it at 4.

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 clause 'Only edited source images' is terse to the point of ambiguity, but the overall structure is tight and readable.

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, externally-publishing mutation the description covers the side effect and the type-match constraint but omits prerequisites (prior sample approval, prepared automation), the role of revision/idempotencyKey, and failure modes — leaving real gaps.

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 4 required parameters, so the description must carry the meaning, and it largely does not. Only automationId is indirectly covered via 'the saved automation type must match this tool'; brandId, revision, and idempotencyKey are never explained, so the agent has no guidance on how revision or the idempotency key affect the call.

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), and the last clause ties it to the edit-image automation type, which helps separate it from the many sibling activate_*_automation tools. It stops short of naming a specific alternative like resume_ or prepare_, but the action is unambiguous.

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 prerequisites ('saved recipe', 'the saved automation type must match this tool') so an agent can infer the automation must already exist and be of the edit-image flavor. It never explicitly says when to prefer activate over resume_/pause_/prepare_ or what state the automation must be in beforehand.

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