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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description still adds genuine context: that previously approved automatic delivery can publish to connected channels (external side effect) and that credit caps govern consumption. Return format is not described but an output schema exists.

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 with the core action front-loaded, followed by the side-effect note and the scoping constraint. Little waste, though the individual clauses are slightly telegraphic.

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 mutation tool with an output schema (so return values need not be explained) the description covers the action and side effects adequately. The gaps are the undocumented parameters with 0% schema coverage and the absence of explicit alternative-tool routing, which leaves an agent under-informed for a destructive, credit-consuming operation.

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 (brandId, automationId, revision, idempotencyKey), so the description must compensate and largely does not. 'saved recipe' loosely gestures at automationId and 'the saved automation type must match' hints at matching semantics, but brandId, revision and idempotencyKey are never explained.

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 pairs the verb 'Activate' with a specific resource ('recurring generation using the saved recipe and credit caps') and adds a scope qualifier ('Only social post artwork') that separates it from text-oriented siblings like activate_post_writer_automation. It stops just short of naming an alternative sibling outright, so it is clear but not maximally differentiating.

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 saved automation type must match this tool' states a prerequisite for calling it, and the delivery sentence hints at what happens after activation. However, there is no explicit when-to-use versus resume_*/pause_*/prepare_* siblings or when-not-to-use guidance, leaving usage largely implied.

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