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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is partly covered. The description adds genuinely new behavioral context: the write performs no generation, spends no credits, and does not publish, and that the saved artifact remains an inactive draft until later activation.

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, front-loaded with the core action and followed by the negative constraints, with no filler. It is efficient, though for a tool with a schema this large the extreme brevity borders on under-specification rather than pure concision.

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?

An output schema exists so return values need no explanation, but for a highly complex nested recipe payload with 0% field documentation the description is far too thin. It omits what a valid recipe requires, the meaning of idempotencyKey, and any prerequisite about existing connections or brand context.

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 recipe parameter is a deeply nested object with dozens of required and optional fields that the description never addresses. The only parameter-adjacent hint is "the saved automation type must match this tool," which does not explain brandId, recipe contents, or idempotencyKey semantics.

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 concrete verb+resource ("Save an inactive review draft") and scopes it to written reel concepts, which separates it from the sample-generation and publish tools. It stops just short of a 5 because it never plainly says it prepares a Reel Concepts automation, leaving the reader to infer the target artifact from the footer constraint.

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?

"Does not generate content, spend credits or publish" gives useful when-not context and implies usage (saving a pre-activation draft), and "the saved automation type must match this tool" hints at a precondition. However, no alternative is named (e.g., update_reel_concepts_automation, activate_reel_concepts_automation, or the generate_sample sibling), so the agent must infer routing.

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