Create Carousel Post

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

The description adds valuable behavioral details beyond annotations: 'Each image is validated and normalized before the upload attempt' and 'Best-effort: modern Facebook may reject cookie-based carousels; failures surface as clear, honest errors.' This exceeds the minimal annotation coverage (idempotentHint, destructiveHint) and provides useful failure-mode context. No contradiction with annotations.

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 appropriately sized: two short sentences for the core purpose plus two sentences for behavioral context. Every sentence earns its place, and the most important information (upload and publish) is front-loaded. No waste.

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?

Given the complexity of a multi-photo publish operation, the description covers the essential action, validation, and potential failure mode. The schema documents parameters and output schema exists. The only minor gap is the lack of explicit mention about the irreversibility of publishing (covered by destructiveHint), but overall it is sufficiently complete.

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%, and the description does not add significant meaning beyond what the schema already provides. The mention of 'multiple photos' loosely aligns with the `sources` parameter, but it does not clarify formats, limits, or the confirm flag beyond schema descriptions. Baseline 3 is appropriate.

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 clearly states the tool's function: 'Upload multiple photos and publish them as one carousel post.' This specific verb+resource phrasing distinguishes it from sibling tools like create_photo_post (single photo) and create_video_post (video).

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 by the phrase 'multiple photos' – it should be used when creating a post with multiple images. However, it does not explicitly contrast with alternatives or state when NOT to use it (e.g., for single photo, use create_photo_post). No exclusions are mentioned.

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