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

The annotations already declare idempotentHint=true and destructiveHint=false, so safety is largely covered. The description still adds real value: it consumes credit caps, it explicitly does not publish, and it requires the saved automation type to match — none of which the annotations convey.

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 terse, front-loaded sentences with essentially no filler; the core action and the key non-publication constraint come first. Slightly clipped in places, but every sentence carries information.

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 annotations cover the safety profile, so the description is not obligated to restate those. Still, for a required-parameter write operation embedded in a large sibling family, the absence of parameter semantics and workflow routing leaves meaningful gaps.

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, yet the description mentions none of them. 'The saved recipe' loosely gestures at automationId but provides no format, role, or constraint detail, 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 (Generate) and resource (a 'paid review sample' for the carousel creator automation), which is clearer than most of the family. However, it never explicitly distinguishes itself from the many sibling variants (prepare_*, activate_*, resume_*, update_*), leaving the agent to infer the workflow position from the name alone.

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 constraints 'Does not publish' and 'the saved automation type must match this tool' imply when it applies, but there is no explicit when-to-use guidance and no routing against prepare_carousel_creator_automation or activate_carousel_creator_automation. 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.