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

Annotations already declare destructiveHint, openWorldHint and idempotentHint, but the description adds real value: it warns that previously approved automatic delivery can publish to connected channels and that credit caps apply (cost/side-effect context). It stops short of naming exactly what is mutated or how revision interacts.

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 tight sentences with the core action front-loaded and no filler. The phrasing is terse to the point of fragmentation, but every sentence carries information.

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?

With an output schema present, return values need not be described, and the side-effect/publishing behavior is covered. Still, key operational details (idempotency, revision meaning, failure modes) are absent for a destructive, open-world mutation.

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 four required parameters (brandId, automationId, revision, idempotencyKey). The description gestures at a 'saved recipe' and 'automation type' but never explains revision, idempotency semantics, or the brand/automation identifiers, so it does not compensate for the 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 (resume) and resource (recurring generation) and even scopes it to the saved recipe/credit caps. The clause 'Only retouched source images; the saved automation type must match this tool' begins to distinguish it from the many sibling resume_* tools, though it does not name them.

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 gives a precondition ('the saved automation type must match this tool') and notes downstream publishing, which implies when the tool applies. However, it never routes the agent to alternatives (e.g., the other resume_* variants) or states explicit when-not guidance, leaving usage largely inferred.

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