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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds real context beyond them: the operation costs credits ('paid', 'credit caps'), it explicitly does not publish, and it only produces original generated images.

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 clauses, front-loaded with the action and its cost/scope constraints. No filler and nothing repeated from the schema or annotations.

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 the description covers cost, non-publication, and type matching. But for a mutating, credit-consuming tool with zero parameter documentation, an agent still lacks guidance on the required revision/brandId semantics and what happens on failure.

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 carries the full burden and mentions none of them. It does not clarify what 'revision' refers to or how the idempotency key interacts with the already-declared idempotentHint.

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?

States a specific verb ('Generate') and resource ('paid review sample') and ties it to the saved recipe, which distinguishes it from prepare_/activate_/update_ siblings. The phrase 'the saved automation type must match this tool' signals it is the image-generator variant specifically, but it never names a sibling tool directly.

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 one important exclusion ('Does not publish') and one precondition ('the saved automation type must match this tool'), which implies a prepare-then-generate flow. However, it never says when to use this vs. the prepare_ or approve_automation_sample tools, so the routing guidance is only implied.

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