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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=true. The description adds useful context: recurring generation, credit caps, and that previously approved automatic delivery can publish to connected channels (a side-effect worth noting). This adds some value beyond annotations, but doesn't explain the destructive/idempotency behavior or what credit caps entail, so it's moderate.

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 concise sentences, front-loaded with the core action. No wasted words, though the final sentence could be integrated more cleanly.

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?

Since an output schema exists, the description needn't explain returns. It covers the action, the type-match precondition, and the publishing side-effect, which is reasonably complete for a mutation tool with annotations carrying the safety profile. However, it omits credit-cap specifics and any parameter guidance for a 4-required-param, 0%-coverage schema.

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% and there are 4 required params, but the description provides no meaning for brandId, automationId, revision, or idempotencyKey. The schema itself has patterns/constraints that imply usage. Baseline for low coverage would push higher, but the description fails to compensate for any of the 4 params, so 3 is appropriate.

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 via the saved automation recipe), and scopes the tool to image backgrounds with the constraint that 'the saved automation type must match this tool'. This differentiates it from siblings like activate_recolor_automation or activate_image_generator_automation, though the differentiation is implied through the type-match note rather than explicit alternatives.

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?

It implies usage via 'the saved automation type must match this tool' and 'Only replacement image backgrounds', giving a precondition. But it doesn't explicitly state when to use this versus the many sibling activate_* tools, nor when not to use it.

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