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

Annotations cover the safety profile (destructiveHint=false, idempotentHint=true, readOnlyHint=false), so the bar is lower; the description still adds genuinely new facts — that generation is unpaid-publish ('Does not publish'), that it draws on saved recipe credit caps, and that a type-match precondition applies. No contradiction with the annotations.

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 with no filler, and the core action is front-loaded ahead of the two constraints. Every sentence contributes a distinct fact (what it makes, that it doesn't publish, the type-match requirement).

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 explained, and annotations carry the safety profile. The remaining shortfall is the undocumented parameter set and the unstated mechanics of 'credit caps' for a credit-consuming generation call.

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%, so the description carries the full burden for four required parameters (brandId, automationId, revision, idempotencyKey). It mentions a 'saved recipe' obliquely but never explains what brandId, revision, or idempotencyKey mean or how they interact with credit caps, leaving all four effectively undocumented.

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?

It states a specific verb and artifact ('Generate a ... sample') and scopes it to one automation type ('Only social post artwork'), which separates it from the ~20 other generate_*_automation_sample siblings. The jargon 'paid review sample' / 'saved recipe' is slightly opaque, and it never names the prepare_/activate_ counterparts directly, so the boundary is inferable rather than explicit.

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 a real precondition ('the saved automation type must match this tool') and an exclusory behavior ('Does not publish'), which pushes it above bare guidance. But it never says when to reach for this versus prepare_social_post_creator_automation, activate_*, or resume_*, so the agent must infer the lifecycle position.

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