create_carousel_post

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

No annotations are provided, so the description must disclose behavior. It mentions creating a container and optional immediate publishing, but does not explain what happens if publish is false (e.g., draft creation), or any other behavioral traits like authentication, rate limits, or destructive potential.

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 extremely concise with only two sentences, no redundant information, and front-loads the core action. Every word serves a purpose.

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 tool with 4 parameters and no annotations or output schema, the description is minimal. It covers the basic purpose but omits important details like how to handle drafts, ordering of items, format constraints for media, or behavior of reply_control. It meets minimum viability but has clear gaps.

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 coverage is 75%, so baseline 3 is appropriate. The description only adds 'Set publish:true to immediately publish', which is already in the schema description. It does not clarify the reply_control parameter (undocumented in schema) or any additional nuances for items or text.

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 specifies the tool creates a carousel post with multiple images or videos, which clearly differentiates it from siblings like create_image_post (single image) and create_video_post (single video). The verb 'create' combined with 'carousel post' gives a specific action and resource.

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 implies immediate publishing with publish:true, but the default is true, so it's slightly misleading. It lacks guidance on when to use this tool versus alternatives, and no prerequisites or constraints are mentioned.

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