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

Annotations already declare the write/idempotent/no-destroy profile, and the description adds real value on top: it states the operation will NOT generate content, spend credits, activate, or publish. 'Reuse the idempotency key' reinforces the idempotentHint. It still omits auth/permission needs, but the negative-behavior disclosure is strong.

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?

Four short, front-loaded sentences; the purpose leads, then constraints, prerequisite, and idempotency guidance. Nothing is padding.

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 an output schema present, return values need not be described, and the description covers purpose, constraints, prerequisite tool, and idempotency. The main gap is that it gives no orientation for filling the complex nested recipe.

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 three required params, including a large nested 'recipe' with many required fields. The description compensates partially by saying the recipe must be complete and that the idempotency key should be reused, but brandId and the recipe's internal fields get no semantic help.

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 ('Save an inactive AI content automation') with state qualifiers ('inactive', 'review delivery') that separate it from update_automation and activate/control siblings. It does not explicitly name a sibling, but the 'inactive' scope makes the intent clear.

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?

'Read capabilities first' points the agent to the get_automation_capabilities prerequisite, and 'supply the complete recipe' sets an input expectation. It lacks explicit when-not guidance or a direct comparison to update_automation, so it stops short of a 5.

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