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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, so the bar is lower. The description still adds genuine context beyond them by noting that previously approved automatic delivery can publish to connected channels (an external side effect) and that generation draws on credit caps.

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, front-loaded with the core action, then side effects, then scope. No padding, though the phrasing is slightly compressed/awkward in places.

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 described, and the description conveys the resume semantics and a key side effect. But for a destructive, idempotent mutation tool with zero parameter documentation, it leaves the meaning of half the inputs unexplained.

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 only vaguely gestures at automationId via 'the saved automation type must match,' and says nothing about what revision or idempotencyKey mean, so it fails to 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 (resume) and resource (recurring generation via the saved recipe), and explicitly scopes it: 'Only social post artwork; the saved automation type must match this tool.' That constraint cleanly distinguishes it from the ~20 sibling resume_* automation tools.

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 implies the context (resuming an existing saved automation of the matching type) but never names alternatives or states when-not to use it, e.g. versus pause_automation, activate_*, or prepare_*. The 'type must match' line is a mild usage constraint but not real routing guidance.

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