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

The annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=true. The description adds valuable behavioral context beyond those annotations: recurring generation, credit-cap consumption, and that previously approved automatic delivery can publish to connected channels.

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?

The description is three front-loaded sentences with no wasted text. Each sentence adds a distinct piece of information: activation scope, publishing side effect, and type restriction.

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?

For a destructive, open-world activation tool, the description covers purpose, side effects, and type constraints, and an output schema exists to cover return values. However, with 0% schema description coverage on four required parameters, it leaves a meaningful gap in how to call the tool correctly.

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 the description does not explain any of the four required parameters (brandId, automationId, revision, idempotencyKey). Terms like 'saved recipe' and 'credit caps' do not map back to the parameters, leaving the agent without parameter guidance.

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 uses a specific verb (activate) and resource (recurring generation / UGC storyboard automation) and explicitly distinguishes this tool from sibling automation types with 'Only UGC storyboard frames; the saved automation type must match this tool.' An agent can identify what the tool does and which automation family it belongs to without opening the schema.

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 clear context for use: a saved recipe, credit caps, and matching saved automation type. It also includes an exclusion ('Only UGC storyboard frames'), but it does not explicitly compare against alternatives such as prepare, resume, or update automation.

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