ig_publish_carousel

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions image count and URL format but does not disclose the asynchronous nature of Instagram publishing, the need to check container status, rate limits, or that the carousel must be published to a valid IG user ID. The absence of annotations and output schema details leaves significant behavioral gaps.

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 concise sentence that front-loads the core purpose and key constraints. However, it could earn a 5 by including a brief mention of usage context or a link to related tools.

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?

The description covers the essential facts (action, object, constraints) but is incomplete for practical use. It lacks guidance on container status polling, publishing limits, and how the output schema relates to the response. Given the complexity of Instagram publishing and the absence of annotations, more context is needed for an agent to use it reliably.

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?

The schema has 0% description coverage and the description only clarifies the image_urls parameter (2-10 public JPEG URLs). It does not explain ig_user_id or caption beyond their names, and caption's behavior (optional, character limits, formatting) is entirely undocumented. The description partially compensates for the low coverage but leaves most parameters underspecified.

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 action (publishes an Instagram carousel) and specifies key constraints (2 to 10 images, public JPEG URLs). It is specific enough to differentiate from ig_publish_image and ig_publish_reel, though it doesn't explicitly name sibling tools.

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 usage for publishing a carousel, and the constraints on image count and URL format provide practical guidance. However, there is no explicit guidance on when to choose this tool over alternatives like ig_publish_carousel_from_files or when not to use it.

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