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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds meaningful behavioral context beyond annotations: it uses credit caps, can publish to connected channels (an external side effect), is limited to written campaign sections, and requires a matching automation type.

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?

The description is three front-loaded, terse sentences with no filler. It could be slightly clearer, but every sentence contributes information about purpose, behavior, or constraints.

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?

For a destructive, idempotent mutation tool with 4 required parameters and 0% schema description coverage, the description is incomplete. It does not explain the parameters, does not clarify what happens on type mismatch, and does not mention usage alternatives, though the presence of an output schema and safety annotations reduces the overall burden.

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 there are 4 required parameters (brandId, automationId, revision, idempotencyKey). The description mentions none of them by name or explains their meaning, formats, or constraints, leaving the agent with no semantic guidance for any parameter.

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?

The description states a specific verb (Activate) and resource (recurring generation using the saved recipe), and ties it to written campaign sections and a matching automation type. This differentiates it from other activate_* tools implicitly, though it does not name alternatives 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?

The description provides a precondition (saved automation type must match) and a scope (only written campaign sections), but offers no guidance on when to use this tool versus related siblings like resume_*, pause_*, or prepare_*. No alternatives or exclusions are named.

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