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

Annotations already declare destructive=true, idempotent=true, and openWorld=true. The description adds genuine context beyond them: activation consumes credits ('credit caps') and previously approved delivery can publish to connected channels, explaining the open-world side effect. It stops short of stating reversibility or retry semantics for the idempotency behavior.

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 compact sentences with the core action front-loaded and the type-match constraint at the end for emphasis. No filler, though the delivery sentence is slightly tangential to activation itself.

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 cover the safety profile. However, for a mutation tool with four undocumented required parameters and a prepare/activate workflow in the sibling set, the description omits prerequisites (e.g., whether the automation must first be prepared or approved) and any parameter detail.

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 4 required parameters (brandId, automationId, revision, idempotencyKey), and the description names none of them. 'Saved recipe' and 'credit caps' gesture at the recipe/revision concept but add no syntax, format, or meaning for any argument, so the description 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?

States a specific verb+resource (activate recurring generation) and adds a scoping constraint — 'Only resized source images; the saved automation type must match this tool' — which lets an agent distinguish it from the many other activate_* siblings. It stops short of naming a competing sibling or stating a hard boundary condition.

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 description implies usage ('Activate recurring generation using the saved recipe') and the type-matching constraint hints at when this tool is appropriate, but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as resume_* or the prepare_/update_ counterparts. Usage is inferred rather than stated.

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