creatives_create_carousel_ad

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

With no annotations present, the description must fully disclose behavioral traits. It only states 'Create', which implies a mutation, but does not mention permissions, side effects, return values, or any validation conditions. This is insufficient for an agent to understand the operational impact.

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 exceptionally concise, consisting of two sentences with no redundancy. The critical card structure is front-loaded, and every word contributes to the tool's purpose. It is appropriately sized given its sparse content.

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 moderate complexity (9 parameters, 6 required, no output schema, no annotations), the description is far from complete. It only covers a fragment of the cards parameter and omits essential information about other parameters, return behavior, and usage conditions. An agent would struggle to invoke this tool correctly without additional context.

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%, so the description must compensate. It partially documents the 'cards' parameter with a structure (link, image_hash, name, description), but leaves it vague with ellipses and entirely ignores the other 8 parameters, including required ones like account_id and page_id. This does not adequately compensate for the lack of schema descriptions.

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 'Create' and a specific resource 'multi-card carousel creative', clearly distinguishing it from related tools like creatives_create_link_ad. The purpose is unambiguous: this tool creates carousel ads.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any use cases, exclusions, or alternative tools. The tool name implies carousel usage, but the description itself offers no explicit or implied context for selection.

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