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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds genuinely new context beyond that: previously approved delivery 'can publish to connected channels' (an external side effect) and that credit caps govern the run.

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 action front-loaded and zero padding. The type-scoping constraint is placed last, which is slightly less prominent than ideal for such a critical precondition, but the text is tight overall.

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 no explanation, and the publishing side effect is disclosed. The remaining gap is parameter meaning: with 0% schema coverage and a mutation tool, an agent still cannot tell what revision or idempotencyKey should contain.

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, so the description carries the full burden and largely fails it. It hints that the automation type is fixed, vaguely gesturing at automationId, but brandId, revision, and idempotencyKey are never explained or tied to the resume/idempotency behavior.

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: 'Resume recurring generation using the saved recipe and credit caps.' It also scopes the tool to a single automation type ('Only images with backgrounds removed; the saved automation type must match this tool'), which distinguishes it from the other resume_* siblings. However, it never explains how 'resume' differs from the closely named activate_background_removal_automation sibling.

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?

The description gives one real precondition ('the saved automation type must match this tool') and implies the tool applies to a paused/saved automation, but it offers no explicit when-to-use guidance versus activate_background_removal_automation or pause_automation. Usage must be inferred from the verb.

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