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

Annotations already declare it is a non-destructive, idempotent write, and the description adds meaningful behavioral context beyond them: no content generation, no credit spend, no publishing, and a type-consistency constraint. It still omits what a 'review draft' state implies for later activation, but this is a solid additive disclosure.

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 no padding; the key framing (save draft) comes first and the caveats follow. The final clause is slightly cryptic and dense relative to the rest.

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 annotations cover the safety profile. However, given an extremely large nested recipe schema and a crowded family of prepare_/activate_/update_ siblings, the description leaves the agent without the prepare-vs-activate-vs-update decision context.

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% and the description explains none of the three required parameters (brandId, recipe, idempotencyKey). The only faint parameter-relevant hint is 'only edited source images', which loosely maps to the attachmentRoles enum, but this does not compensate for a completely undocumented nested recipe object.

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 artifact: 'Save an inactive review draft' for the edit-image automation family. The clause 'the saved automation type must match this tool' makes the resource scope explicit, though it never names the activation/update siblings it must be distinguished from.

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 useful negative guidance ('Does not generate content, spend credits or publish') which implies this is a pre-activation step, but never names alternatives such as activate_edit_image_automation or update_edit_image_automation, nor states the condition that selects this tool over them. Usage is implied, not stated.

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