create_carousel_post

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

With no annotations, the description carries the burden of disclosing side effects and behavior. It only restates the max item limit (already in schema) and includes a date reference. It does not state whether the post is published immediately, requires authentication, or what the response contains.

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 a single sentence, efficient and front-loaded. However, the parenthetical '(September 2024 update)' is extraneous and not actionable for an agent, slightly reducing the score.

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 nested carousel_settings, four parameters, and no output schema, the description is too minimal. It doesn't clarify whether the post is published immediately or drafts, what the return value is, or how to handle failures. This is inadequate for the tool's complexity.

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 descriptions cover all top-level parameters (media_urls, text, alt_texts, carousel_settings). The description adds minimal extra meaning beyond repeating the 20-item limit, so baseline 3 is appropriate as the schema does the heavy lifting.

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 identifies the action (create), the resource (multi-media carousel posts), and a key constraint (up to 20 items). It distinguishes from sibling tools like create_thread_chain or create_post_with_restrictions by focusing on the carousel nature.

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 provides no guidance on when to choose this tool over alternatives. It doesn't mention exclusions, prerequisites, or comparisons with sibling creation tools. Given the many creation siblings, this is a gap.

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