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

With annotations already declaring destructiveHint=true and readOnlyHint=false, the description adds meaningful behavior: it saves only one format, preserves other formats, and requires a fresh read receipt for hosted edits. It is clear about the single-screen constraint, though it does not spell out what happens to an existing layout for the target format.

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?

The description is three tight sentences with no filler. It front-loads the core action first, then gives the read-receipt prerequisite, then the layout constraint and preservation behavior.

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 complex 7-parameter save tool with nested layout objects and an output schema, this is largely complete: it covers scope, prerequisites, and key layout constraints. Minor omissions such as explicit alternative-tool routing and overwrite semantics for the target format keep it from a 5.

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 71%, so the schema already documents most parameters. The description adds value by clarifying that layout must contain exactly one screen at the format's canvas size and that readReceipt is for hosted use, but it leaves format enum details and the projectId/generationId alias relationship to the schema.

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 specific verb and resource: saves one complete social or store-creative format layout for a variant and language. It distinguishes this partial per-format save from a whole-graphics save by noting that other formats are preserved, though it does not name the sibling alternative explicitly.

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?

It gives important usage conditions—hosted edits need a fresh same-format read receipt and the layout must contain exactly one screen—but it does not explicitly say when to use this tool instead of save_graphics, save_layout, or the related apply/transform tools.

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