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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds real beyond-annotation context: the recipe is REPLACED, the previously reviewed sample is INVALIDATED, and no generation/publishing occurs. This discloses what state is destroyed, which the annotations alone do not.

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, front-loaded sentences with the primary action first and constraints after. 'Only enhanced source images' is slightly cryptic but still earns its place as a scope limiter.

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 explained, and the description covers the key behavioral traits (replace, invalidate, no generation). However, for a nested-object mutation tool with five undocumented required params, the description leaves meaningful gaps around revision/idempotency 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%, so the description carries the full burden for 5 required params. It only hints at the 'recipe' (replaced wholesale) and the type-match constraint; it never explains 'revision', 'idempotencyKey', or 'brandId', and gives no guidance on the nested recipe fields or attachmentRoles. This does not compensate for the coverage gap.

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: 'Replace this automation's recipe and invalidate its reviewed sample.' It further scopes the tool by requiring that 'the saved automation type must match this tool,' which tells the agent this only applies to image-enhancer automations. It stops short of naming a specific sibling (e.g. update_image_generator_automation) as the alternative.

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?

Gives clear context for when to use it ('replace recipe', 'invalidate reviewed sample') and two exclusion signals: 'Does not generate or publish' and the type-match precondition. It doesn't explicitly say which sibling to use for a different automation type, leaving that inference to the agent.

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