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

Annotations already state destructiveHint=false and idempotentHint=true, so safety is covered; the description adds genuinely new context: the draft is saved inactive, no content is generated, no credits are spent, and nothing is published. That is exactly the kind of side-effect disclosure the annotations cannot express, though it says nothing about permissions, validation failures, or what the saved draft returns.

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 action, then the behavioral exclusions, then the scope constraint. No filler or restated schema content.

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 not be explained, and the annotations carry the safety profile. However, for a tool whose main input is a 30+ field nested recipe, the description gives no orientation on how to construct that payload or on idempotencyKey usage, leaving a substantial gap.

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 description explains none of the three top-level parameters (brandId, recipe, idempotencyKey) nor the large nested recipe object. With a deeply nested, constraint-heavy payload and no per-property documentation, the description should have compensated but does not.

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 concrete action ("Save an inactive review draft") and constrains scope ("Only written social posts; the saved automation type must match this tool"), which distinguishes it from the other prepare_* automation variants. It never names the resource as a 'post writer automation' explicitly, leaving the agent to infer it from the tool name plus the 'written social posts' clause.

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?

Usage is implied (create an inactive draft for later review) but there is no explicit when-to-use vs the alternatives in the sibling set (activate_post_writer_automation, update_post_writer_automation, generate_post_writer_automation_sample). The negative clauses ('does not generate content, spend credits or publish') describe behavior rather than tool selection.

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