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

Annotations already declare write, destructive, idempotent, and open-world. The description adds valuable context beyond that: credit caps are consumed, previously approved automatic delivery can publish to connected channels (an external side effect), and only background-removed images are eligible. Missing auth/permission details, but strong given 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 tight sentences, front-loaded with the action and its purpose. Every sentence adds either behavior or a constraint. Minor awkwardness in 'Previously approved automatic delivery can publish to connected channels' but no filler.

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?

With a rich annotation set and an output schema, the description need not cover return values. It covers domain constraint and delivery behavior, but leaves parameter meaning and activation prerequisites unexplained, which matters for a 4-parameter mutation tool with 0% schema coverage.

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 the description mentions no parameter names or semantics. It does not explain brandId, revision, or idempotencyKey, and only loosely implies that a saved automation (automationId) is needed. No compensation 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 the specific action (Activate) and resource (recurring generation using the saved recipe), and distinguishes itself from the many sibling activate_* tools by requiring 'the saved automation type must match this tool' and constraining to 'Only images with backgrounds removed'. It does not name a specific alternative sibling, so not a 5.

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?

Implies usage via the constraint that the saved automation must be of the background-removal type, but never states when to use this versus prepare_, pause_, or resume_ variants, nor any prerequisites like having a prepared sample. No explicit when-not guidance.

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