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 useful context beyond them: it consumes 'credit caps' and that approved delivery can 'publish to connected channels', explaining the open-world side effect. It does not spell out irreversibility or what gets destroyed on reactivation, so not a 5.

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 sentences with the action front-loaded and no filler. The final constraint sentence is dense but earns its place; structure is efficient.

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?

Output schema exists so return values need not be described, and the activation/publishing behavior is covered. But for a destructive, idempotent mutation with 0% param coverage, the absence of any revision/idempotencyKey guidance leaves a real gap for an agent trying to call it correctly.

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, so the description carries the full burden — but it explains none of brandId, automationId, revision or idempotencyKey. 'Saved recipe' loosely gestures at automationId, but the versioning (revision) and idempotency semantics are entirely absent.

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 ('Activate') and resource ('recurring generation using the saved recipe'), and the closing clause ('Only vertical story artwork; the saved automation type must match this tool') scopes it away from the many sibling activate_* tools. Clear what the tool does, though the type-matching constraint is the only differentiation and could be crisper.

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?

Provides an implied prerequisite — the saved automation must already exist and its type must match — plus a note that 'previously approved automatic delivery can publish to connected channels'. However it never names alternatives (resume_/update_/prepare_story_creator_automation) or states when NOT to use this activation path.

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