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 mutation/side-effect profile is partly covered. The description adds real value by disclosing that approved automatic delivery can publish to connected channels and that credit caps are consumed. It does not explain what makes activation destructive or how to reverse it.

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 effect. No filler, though 'Only written reel concepts' is awkwardly worded and slightly opaque.

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 description covers the main behavioral concerns (publishing, credit consumption, type matching). The significant gap is the complete absence of parameter semantics for a 4-required-param mutation tool.

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 undocumented in the schema. The description only loosely gestures at automationId via 'the saved automation type must match this tool' and never addresses revision or idempotencyKey, 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?

The description states a specific verb+resource: 'Activate recurring generation using the saved recipe and credit caps.' It also scopes the tool ('Only written reel concepts; the saved automation type must match this tool'), which distinguishes it from the many sibling automation tools. It stops short of naming the closest siblings (resume_/prepare_reel_concepts_automation), so it is clear but not fully disambiguating.

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?

'Activate recurring generation' implies when to use it, and 'the saved automation type must match this tool' is a light precondition. However, there is no explicit guidance on when to activate vs. resume, prepare, or pause the same automation, all of which exist as siblings. Usage is implied rather than stated.

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