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

Annotations already declare this is a non-read-only, idempotent, non-destructive, open-world call, so the bar is lower, yet the description adds real signal: 'paid' implies credits are consumed, 'credit caps' implies a quota ceiling, and 'Does not publish' clarifies the state effect. It stops short of stating permission/auth requirements or what happens on cap exhaustion.

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, front-loaded sentences with zero filler: the action, the non-publication fact, and the input constraint. Efficient, though the final clause is slightly cryptic in isolation.

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 the credit/publish semantics are covered. However, for a write operation with 0% parameter documentation and no auth or failure-mode notes, the description leaves real gaps an agent would need.

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. The description loosely maps 'saved recipe' to automationId and 'automation type must match' to the automation, but revision and idempotencyKey — the parameter that governs safe retry — are never explained, leaving the burden entirely on bare patterns in the schema.

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+resource ('Generate a paid review sample') and names the inputs (saved recipe, credit caps), which is more than a name restatement. The clause 'the saved automation type must match this tool' helps an agent distinguish it from the ~20 sibling generate_*_automation_sample tools, though it never names one explicitly.

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?

'Does not publish' and 'Only enhanced source images' imply the boundaries of this operation, but there is no explicit when-to-use framing or routing to alternatives (e.g., when to use generate_edit_image_automation_sample versus this one). Usage is inferable but not stated.

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