Publish a carousel

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

The description goes well beyond the annotations by disclosing that each item is staged separately, transcoded in parallel, then bound by a parent container; that it counts as a single post against the daily quota; and that the result is public and irreversible, requiring confirm: true. This aligns with destructiveHint=true and adds meaningful context.

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 sentences, front-loaded with the primary purpose, then concise behavioral context. Every sentence adds relevant information: item range, internal staging/transcoding process, quota impact, and irreversibility/confirmation requirement. No filler.

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 destructive publish action with no output schema, the description covers the essential invocation concerns: media type and count, processing behavior, quota accounting, irreversibility, and the mandatory confirm flag. Combined with rich per-parameter schema descriptions and annotations, this is sufficient for an agent to select and invoke the tool correctly.

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 100%, so the schema already documents all six parameters thoroughly. The description reinforces the 2-to-20 item constraint and explains why confirm must be true, but it does not add materially new parameter-level meaning beyond what the schema provides.

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 ('Publish'), a specific resource ('2 to 20 images or videos as one carousel post'), and clear constraints. It distinguishes this from single-post or thread-publishing siblings by emphasizing the carousel format and item range.

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 description clearly implies this is the tool for publishing a multi-item carousel of 2 to 20 media items. It does not explicitly name alternatives like create_post or publish_staged, but the scope is clear enough that an agent should not confuse it with single-post tools.

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