publish_carousel

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

Annotations only declare the generic safety profile (not read-only, not destructive, open-world). The description adds non-obvious behavior beyond that: the post is public and immediate, preview mode sends nothing, images are cropped to the first image's aspect ratio, and each call consumes one daily post quota.

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?

Front-loaded with the action and usage gate, then structured Args/Returns/Limits sections with no filler. Mild redundancy between the confirm workflow described above and the Args entry for confirm, but nothing that wastes meaningful space.

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 mutating, quota-consuming, multi-image publish tool this covers everything an agent needs: constraints, confirmation workflow, quota impact, and return payload. An output schema exists, so the returns line is bonus rather than required.

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%, yet the description supplies real semantics for all three params: image_urls gets a 2-10 count constraint and ordering/crop rule (none of which the schema encodes), confirm's default and effect, and caption's purpose. Only the caption limits are delegated to a sibling reference, a minor gap.

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 and resource (publish a carousel) and immediately clarifies what a carousel is ('several photos in one post'), which distinguishes it from the sibling publish_image tool. 'Public and immediate' adds scope detail an agent can act on.

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?

Explicit when-to-use gate: 'Use only when the user explicitly asks to post several photos together.' It also prescribes the correct invocation sequence (confirm=false preview, then confirm=true after user approval), which is the key decision an agent must get right here.

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