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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond annotations: resuming consumes credit caps and can auto-publish previously approved delivery to connected channels, plus the type-matching precondition. It still does not explain what the destructive aspect entails, which keeps it out of the top score.

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 action and free of padding. The final fragment ("Only resized source images") is slightly telegraphic but still earns its place as a scope guard.

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 mutation's side effects are partially covered. But for a destructive, 4-required-param mutation with zero schema description coverage, the description leaves parameter meaning and the nature of the destructive effect unexplained, which is a notable gap.

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), so the description must compensate and it largely does not. It never names or explains any parameter; only the loose phrase "the saved automation type must match" gestures at automationId without clarifying revision or idempotencyKey semantics.

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 gives a specific verb+resource ("Resume recurring generation") and adds a scope constraint ("Only resized source images; the saved automation type must match this tool") that helps distinguish it from the many sibling resume_*_automation tools without naming one. It is clear, but it never names a sibling or the exact automation type (smart resize) in a way that routes the agent explicitly.

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 constraint "the saved automation type must match this tool" implies when this tool applies and implicitly excludes other automation types, which is useful. However, no alternative is named (e.g., activate_* vs resume_*), and there is no explicit when-to-use/when-not statement, so usage is left largely to inference.

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