create_carousel_batch

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

No annotations are present, so the description carries the full burden. It explains the core behavior (splitting content into batches) and the input format, but lacks details on permissions, side effects, or error handling that would be useful for a mutation tool.

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 succinct and well-organized: a one-sentence purpose, followed by parameter explanations and a helpful example. Every sentence earns its place without redundancy.

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 3-parameter create tool with no output schema, the description covers inputs, splitting logic, and naming. It could hint at how to obtain content_ids (e.g., from sister tools) or potential errors, but is otherwise 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 0%, but the description fully compensates by explaining each parameter: content_ids format, batch_name optionality, and images_per_post default/max/behavior. The example further clarifies semantics, adding significant meaning beyond the bare schema.

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 verb 'create' and the resource 'carousel batches', mentioning the input source ('selected images or PDF pages'). This distinguishes it from sibling tools like post_carousel_to_instagram (posting) or list_carousel_batches (listing).

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?

Provides clear context that this tool creates batches rather than performing other operations, and includes an example showing how images_per_post affects batch count. However, it does not explicitly mention when to use this tool over alternatives or state any exclusions.

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