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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=true, so the safety profile is covered. The description earns credit by adding context beyond them: it discloses that previously approved delivery can publish to connected channels and that generation draws on credit caps, both of which are real consequences an agent should weigh before calling.

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 no filler. The final clause is mildly redundant with the tool name but still carries the type-matching constraint, so nothing is wasted outright.

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 annotations carry the safety profile. However, with four required parameters at 0% schema coverage and no mention of revision-based concurrency or idempotencyKey semantics, the definition is thin for a mutation tool an agent must invoke correctly on the first try.

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 all four parameters (brandId, automationId, revision, idempotencyKey) are required but completely undocumented. The description mentions 'the saved recipe' only obliquely and never explains any parameter, so it does not compensate for the coverage gap at all.

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?

The description opens with a specific verb+resource ('Resume recurring generation') and scopes the operation to advertising artwork, which separates it from the many sibling resume_* tools that target other automation types. It does not, however, explicitly name the alternative families (activate_*, pause_automation) it overlaps with, so sibling differentiation rests partly on the tool name itself.

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?

'Only advertising artwork; the saved automation type must match this tool' gives an applicability constraint that rules out other automation categories. It stops short of telling the agent when to resume versus activate, or what state the automation must already be in, leaving the resume-vs-fresh-start distinction implicit.

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